I go through about 25 cybersecurity news portals and blogs every week and pull out the most interesting stories. Then I turn them into this short, digestible summary, so you can stay up to date without trying to follow 25 different sources yourself. 😱
My aim is to create a summary that gives you the gist without needing to open up the source article. But if you do want to dig deeper, all the sources covering the event are linked below each story.
If you enjoy these, come back next Monday
scroll to the bottom to subscribe to the e-mail newsletter.
Revolut disclosed customer data leaked after the attackers asked nicely
Revolut says a third party impersonating a government agency used a legitimate government-domain email account to submit fraudulent customer data requests, leading to disclosure of sensitive user information. Scammers leveraged the trust and urgency around law-enforcement/government inquiries—rather than exploiting Revolut’s systems—to obtain regulated financial and identity data.
Key Details
- A Revolut spokesperson confirmed to TechCrunch that a “limited” number of customers were impacted and said the company had contacted those customers directly.
- Revolut, however, did not disclose the exact number of impacted individuals.
- It also did not answer whether the incident was limited to a specific market and declined to disclose the government agency involved.
- Data exposed included identity documents and biometrics: names, addresses, phone numbers, email addresses, dates of birth, occupation, copies of passports/driver’s licenses, and verification selfies.
- Financial data was also disclosed, including IBANs, account statements, withdrawal records, and full transaction history (including Bitcoin-related activity).
- The request carried valid technical domain credentials and was processed as an authentic government inquiry, according to Revolut’s statements to affected users and to reporters.
Next Steps
- When making verification selfies, consider that eventually humans might see the photo.
- Treat government/law-enforcement data requests as high-risk: require out-of-band verification of requester identity (call-back to published numbers, validated portal, or pre-registered contacts) before releasing any customer data.
- Add a second-person approval and documented legal review for “emergency” or time-pressured requests, even when they originate from legitimate-looking government domains.
Read more at Talkback.sh, The Record
Compromised verified HBO Max Reddit account ran 108 ClickFix malvertising ads that tricked users into installing info-stealers
Attackers hijacked the verified u/hbomax Reddit account and ran 108 malicious ads in 48 hours that drove users to lookalike software download pages using a ClickFix prompt to get victims to copy/paste and execute attacker-supplied commands. The campaign, tracked as PasteSwitch, used that “user-executed command” handoff to deliver macOS stealers (and persistence) and Windows payloads via mshta/PowerShell, including Amatera Stealer and crypto address clippers.
Key Details
- The 48-hour ad burst grouped lures across multiple domains and themes, including hbomaxx[.]us / hbomaxx[.]app (HBO Max), codex-craft[.]com (Codex), and apple.clean-disk-guide[.]com (macOS utility), leveraging the trusted identity of a verified brand account.
- On macOS, PasteSwitch pages displayed a copied command that fetched a remote script (example: curl xxx piped to zsh) and reported execution via telemetry endpoints before retrieving a native payload.
- Analysis of the September macOS payload described theft of credentials/cookies and other data plus macOS persistence using Apple-lookalike paths
- For Windows targets, lures used mshta to bootstrap an obfuscated PowerShell chain that ultimately loaded Amatera Stealer
- Researchers linked the HBO Max ads to a broader PasteSwitch ecosystem that also delivered crypto clippers.
Next Steps
- Identity trust is increasingly valuable asset to be exploited. Make sure you have an inventory of externally trusted identities that could be abused to impersonate the company, and clear security controls for their protection defined.
- Compromised advertising accounts can distribute malicious content at scale before anyone notices. Set up monitoring or regular reviews to detect unexpected campaigns, ads, destination URLs, and spending across the advertising platforms your company controls.
Read more at ADAMnetworks, Talkback.sh, Cybersecurity Reddit
CISA issues first guidance for critical infrastructure on using cyber decoys to detect intruders already inside networks
CISA published a new guide on deploying cyber decoys—phony systems, accounts, and data—to distract attackers and generate high-fidelity detection when they interact with assets that should never be touched. The agency positions decoys as a low-cost complement to zero trust and “assume compromise,” aimed at catching adversaries who blend in by using legitimate credentials and living-off-the-land techniques.
Key Details
- CISA defines cyber decoys as assets that look real but are built to distract adversaries, detect their presence, and collect cyber threat intelligence (CTI).
- The guidance recommends placing decoys where normal users rarely/never go and tuning them to produce high-confidence alerts rather than noisy detections.
- CISA describes a three-phase operating model—preparation, execution, and learning/feedback—including setting goals, mapping desired attacker perceptions, defining deployment channels, and measuring success.
- The guide covers multiple decoy techniques—lures, tripwires, decoy artifacts, honeytokens, and honeypots—and includes example deployment scenarios to illustrate use.
- CISA leadership emphasized decoys can be incremental, scalable, and feasible for resource-constrained critical infrastructure owners, including creating simple honeytokens internally.
Next Steps
- Review CISA’s guide and pilot one decoy type (e.g., honeytokens) in low-traffic areas to validate alert fidelity and response handling: https://www.cisa.gov/sites/default/files/2026-09/using-cyber-decoys-to-strengthen-detection-and-response_508c.pdf
- During planning, define success metrics and the specific attacker behaviors you want to surface (e.g., credential discovery, lateral movement, data access) so decoy interactions translate into actionable intelligence.
Read more at Talkback.sh, Cyberscoop
OpenAI hires contractors to review real ChatGPT chats, which can include sensitive personal information
404 Media reports that OpenAI is hiring hundreds of contractors to read and rate real users’ ChatGPT prompts and conversations to improve the model’s responses. OpenAI says it attempts to remove personal information before prompts reach reviewers, but acknowledges sensitive details can still pass through.
Key Details
- Reviewers reportedly see a high-volume stream of real prompts, sometimes including entire user conversations, which may contain sensitive personal details.
- According to the report, contractors’ tasks include critiquing and rating ChatGPT’s generated replies as part of response-quality improvement workflows.
- Internal documents cited by 404 Media describe guidance aimed at reducing anthropomorphism and “sycophantic” behavior in model outputs.
- The article says contractors do not see users’ ChatGPT usernames, and OpenAI claims to try to remove personal data before review.
- Anthropic told 404 Media it also uses human review to improve its models.
Read more at 404 Media
Single malicious extension can hijack built-in “agentic” browser AIs across Chrome, Comet, Edge, Opera Neon, and Claude for Chrome
Researchers demonstrated that one ordinary Chromium extension can seize control of multiple browsers’ built-in AI assistants by injecting itself into the trusted “brain” web origin those assistants listen to, then issuing commands as if it were the vendor. The technique uses common extension capabilities (notably declarativeNetRequest) to alter headers and redirect scripts, enabling prompt-forcing and (depending on product) access to sensitive data or agentic actions.
Key Details
- Scope and status: the report describes demonstrations (not in-the-wild exploitation) and assumes the victim has already installed the attacker’s extension; Forever Security reports ~$20K in bounties and two CVEs across the five products.
- Demonstrated impacts varied by product: Chrome and Comet were shown reading local files; Chrome additionally could access camera/microphone; Comet could leak browsing history and take screenshots; Comet/Edge/Opera Neon/Claude for Chrome could be driven to perform agent actions via forced prompts.
- Chrome “Gemini Live” (CVE-2026-0628, CVSS 8.8): a Chromium WebView handling gap allowed declarativeNetRequest rules to affect embedded Gemini pages, enabling script injection into the trusted context.
- Edge Actions (CVE-2026-55945, CVSS 4.2): the attack abused a Microsoft Edge marketing page capability (sendCopilotQuery) plus a race condition around the “edgeTools” setting to force an actionable prompt.
- Perplexity Comet exposure hinged on externally_connectable overreach: Comet’s built-in agent extension allowed connections from multiple Perplexity domains, and a less-protected “testing” domain could be leveraged to reach the agent and issue commands.
Next Steps
- Consider having a strict extension allowlist.
Read more at microsoft.com, Talkback.sh, Dark Reading, The Hacker News
Cisco Secure Email Gateway bug lets attackers trigger root command execution via crafted emails (CVE-2026-76461), exploited in the wild
Cisco patched an actively exploited unauthenticated SQL injection in Secure Email Gateway that can lead to root command execution when the appliance parses a crafted email containing malicious SQL. Fixed releases are available, and Cisco notes attackers with root access may be able to remove evidence of compromise.
Key Details
- The flaw affects Cisco Secure Email Gateway physical and virtual appliances in any configuration; Cisco says Secure Email and Web Manager and Secure Web Appliance are not affected.
- Cisco PSIRT reported it became aware of active exploitation in September 2026; Cisco Secure Email Cloud customers with signs of compromise were contacted and Cisco says it has upgraded all Secure Email Cloud devices to 16.5.0-780.
Next Steps
- Upgrade Secure Email Gateway to a fixed AsyncOS release (15.5.5-014 / 16.0.4-302 / 16.5.0-780).
Read more at sec.cloudapps.cisco.com, sec.cloudapps.cisco.com, The Hacker News, CSO Online, Cyberscoop, Talkback.sh, Kudelski Security
GitHub Actions adds cache-mode to enforce least-privilege cache access and reduce cache poisoning risk
GitHub added cache-mode controls that restrict whether a workflow/job can read from and/or write to the Actions cache, aiming to curb cache poisoning used in supply-chain compromises like Ultralytics (2024) and TanStack (2026). GitHub also highlighted that build provenance/attestations can still “pass” when a build restores a tampered cache entry, because the attestation reflects where the build ran—not the integrity of cached inputs.
Key Details
- Cache poisoning happens when a cache entry written in one context is restored and executed in another, letting an attacker who can write to a cache key plant artifacts/dependencies that later run with a trusted workflow’s permissions and secrets.
- cache-mode supports four values: read, write, write-only, and none; GitHub notes read is the default for lower-trust events like pull_request_target, while write is the default for trusted events like push.
- Job-level cache-mode overrides workflow-level, and GitHub says the cache service enforces the mode rather than relying on action-side behavior.
- In reusable workflows, a called workflow cannot receive more cache access than its caller grants, preventing privilege escalation through reuse.
- GitHub recommends cache-mode: none for AI agent workflows that may execute untrusted input (e.g., issue/PR text), citing agent-driven scenarios like the Cline incident described as involving suspected cache poisoning.
Next Steps
- Set cache-mode: read for low-trust triggers (e.g., pull_request_target) and avoid granting write/write-only on those events unless you explicitly accept the poisoning risk.
- For workflows that do not need caching (especially agent-driven automation), apply cache-mode: none at the workflow or job level to remove cache access entirely.
- Where you do need to populate caches, consider using write-only in jobs that should save artifacts but must never restore from cache.
Read more at Socket.dev, github.blog
Subscribe
Subscribe to receive this weekly cybersecurity news summary to your inbox every Monday.