Light

Episode #1051 Quiz

Amazon Sues Perplexity
Date: 2025-11-11 | Length: 2.5 hrs | Episode page at twit.tv

About this episode

Security Now! Episode 1051 discusses Amazon’s lawsuit against Perplexity for its AI-powered Comet browser automating shopping on Amazon without identifying itself, raising questions about AI agency and website control. Nevada demonstrated effective ransomware recovery without paying ransom. Check Point revealed a $128 million DeFi exploit from a rounding error.

Your name and email are stored only in your browser local storage for convenience. They are not retained server-side.

NameEmail

Question 1: What specific vulnerability allowed the attacker to drain $128 million from the Balancer V2 DeFi platform, as discussed in this episode?

Question 1

What specific vulnerability allowed the attacker to drain $128 million from the Balancer V2 DeFi platform, as discussed in this episode?

A SQL injection vulnerability in the user authentication service allowing unauthorized access. A buffer overflow in the smart contract that crashed the platform and exposed funds to attackers. A rounding error vulnerability in the _upscaleArray function leading to compounded precision loss during batchSwap operations. Exploitation of a weak cryptographic key in the DeFi wallet generating unauthorized token transfers.

Question 2: According to the episode, what is the main reason Google Chrome started autofilling driver's license numbers and passport info in its autofill feature?

Question 2

According to the episode, what is the main reason Google Chrome started autofilling driver's license numbers and passport info in its autofill feature?

Because browsers anticipate an increase in websites requesting government-issued identification, indicating a shift in identity verification online. To replace password managers by storing all credentials including IDs locally on the browser. To comply with new government regulations requiring browsers to assist with official document entry. Because Chrome integrated a partnership with DMV databases to automatically fetch and fill these numbers.

Question 3: What was the key factor behind the State of Nevada's successful ransomware recovery highlighted in the episode?

Question 3

What was the key factor behind the State of Nevada's successful ransomware recovery highlighted in the episode?

Refusing to pay ransom while relying on strong backups, in-house recovery effort, and use of pre-established incident response playbooks. Rolling back to an older uninfected backup without engaging law enforcement or forensic investigation. Immediately paying a moderate ransom to receive decryption keys and quickly restore systems. Outsourcing the entire recovery to a third-party contractor to expedite restoration.

Question 4: What side-channel information did Microsoft identify as a risk for leaking sensitive topics in LLM (Large Language Model) conversations?

Question 4

What side-channel information did Microsoft identify as a risk for leaking sensitive topics in LLM (Large Language Model) conversations?

Unencrypted plaintext logging on client side causing data leakage. Weakness in TLS cryptographic algorithm allowing decryption of content. Encrypted TLS packet sizes and timing patterns in streaming mode responses. Network IP address correlation to user identity without encryption weaknesses.

Question 5: What critical policy change did the State of Nevada implement to prevent further damage after the ransomware attack?

Question 5

What critical policy change did the State of Nevada implement to prevent further damage after the ransomware attack?

Automatically paying ransom if backup volumes were encrypted to regain access quickly. Reinstalling all operating systems from scratch without forensic investigation. Isolating affected virtual machines immediately upon detection to prevent lateral spread. Disabling all remote desktop protocol (RDP) access for all users indefinitely.

Cancel

My Data//Security & Privacy//Clear Local Data

© 2026 Ken ArmstrongSecurity Now™ is a trademark of TWiT LLC. All trademarks and copyrights of the Security Now podcast are respected and reserved to their respective holders.
This is a hobby project made with love and admiration for what Steve Gibson and Leo Laporte have built over 20 years.