Last updated: October 5, 2026 at 10:28 AM UTC
All 897 Vulnerability 362 Breach 144 Threat 384 Defense 7

Chipmaker Analog Devices confirms a breach and stolen files, says operations are fine

Analog Devices, a major US semiconductor maker, confirmed in a securities filing that an unauthorized party accessed some internal systems and exfiltrated files in a June intrusion, while saying operations were not affected. The company has not named who was responsible. Days before the filing, an extortion group calling itself ExfilSquad listed Analog Devices on its leak site and claimed to hold about 570,000 customer records with personal information and home addresses, but Analog Devices has not linked the June breach to that group, and the claim is unverified. The filing also noted a second, separate security issue unrelated to the June intrusion.

Check
Organizations that share data with Analog Devices should watch for a notification and monitor for phishing, while treating the extortion group's specific claims as unverified until the company confirms details.
Affected
Analog Devices and parties whose data sat in its systems; the company confirms files were stolen in June, while an extortion group's claim of 570,000 customer records with home addresses remains unverified.
Fix
Affected parties should watch for official notice and be alert to targeted phishing. Organizations should segment sensitive data, limit what vendors can reach, and prepare for extortion-driven leaks and unverified claims.

Hidden text in a Word file makes Copilot alter data and spread the payload

A researcher disclosed a prompt-injection technique that turns Microsoft 365 Copilot for Word into a carrier for self-spreading instructions. Malicious commands hidden as tiny white-on-white text in a document are invisible to a reader but read in full by Copilot when the file enters its context during a drafting or editing task. Copilot then follows them, in one example silently altering financial figures in a report, and copies the same hidden instructions into the new document, which becomes a fresh carrier for the next person who uses it. It does not spread on its own, but Microsoft's mitigations over 144 days blocked specific wordings without fixing the underlying class.

Check
Treat documents from outside as untrusted input to AI assistants, and review how Copilot and similar tools are used on shared or externally sourced files that may carry hidden instructions.
Affected
Organizations using Microsoft 365 Copilot for Word on documents from outside sources; hidden instructions can make Copilot tamper with content, such as financial figures, and propagate into newly created files.
Fix
Limit AI drafting on untrusted documents, review AI-edited outputs for unexpected changes, strip hidden text from incoming files, and press vendors for controls that separate document content from instructions.

Amazon ties the chalk and debug npm hijacks to North Korean hackers

Amazon's threat intelligence team linked several major npm supply chain attacks to a North Korean group tracked as Sapphire Sleet, also known as BlueNoroff. The group compromised the small typo-crypto package in March 2025 as a test, then hijacked the hugely popular debug and chalk packages in September 2025, and axios in March 2026. The debug and chalk incident, which pushed a wallet-draining script into packages with billions of weekly downloads, reached roughly one in ten cloud environments within two hours. The attackers gained access by phishing package maintainers through lookalike npm domains, then published malicious versions that auto-installing projects pulled in.

Check
Review whether your projects or CI pulled compromised versions of typo-crypto, debug, chalk, or axios during the affected periods, and check developer and build environments for wallet-draining or credential-stealing behavior.
Affected
Developers and organizations that auto-install npm dependencies; a phished maintainer account can push a malicious version of a hugely popular package that reaches thousands of downstream environments within hours.
Fix
Pin and verify dependencies, add a delay before adopting new versions, watch for maintainer-account phishing, protect publishing accounts with phishing-resistant MFA, and monitor build environments for credential and wallet theft.

Fake IT support calls on Microsoft Teams end in Chaos ransomware

Sophos detailed a campaign, tracked as STAC4749, in which attackers impersonate IT help desk staff over Microsoft Teams to talk employees into granting remote access, then deploy Chaos ransomware. Using external Teams accounts, the operators start chats and voice calls claiming to fix an urgent problem, persuade the target to open a remote support session, and run PowerShell to pull down a modular toolkit for persistence and lateral movement. Between February and June 2026 they hit dozens of North American organizations, about 95 percent in the US and Canada, across services, manufacturing, energy, and construction. In one case they went from first contact to encrypting files in under seventeen hours.

Check
Restrict or block messages and calls from external Microsoft Teams accounts, and tell staff that real IT support will not cold-call them over Teams to request remote access.
Affected
North American organizations whose staff can be reached by external Teams accounts; attackers posing as IT support talk employees into remote access, then move laterally and deploy Chaos ransomware, sometimes within hours.
Fix
Lock down external Teams contact, train staff to verify support requests through known channels, monitor for unexpected remote-access tools and suspicious PowerShell, and audit startup and registry entries for persistence.

Cisco patches exploited Firewall Management Center flaw that grants built-in account access

Cisco has patched a flaw in Secure Firewall Management Center that attackers were already exploiting to log into devices. Tracked as CVE-2026-20316, it stems from static credentials for a low-privilege account built into the software, letting an unauthenticated remote attacker sign in and read sensitive data. Cisco scored it 5.3 but rated it High because the access can be chained with other flaws to escalate privileges. In the same cycle it patched CVE-2026-20079, a separate critical authentication bypass that reaches root, and shipped one set of hot fixes with a shared indicator suggesting the two could be combined. There are no workarounds.

Check
Upgrade Secure FMC to a fixed release now, and check for compromise by searching device logs for references to /var/tmp/license.tmp, which Cisco lists as an indicator.
Affected
Organizations running Cisco Secure Firewall Management Center releases 7.0, 7.2, 7.4, 7.6, 7.7, or 10.0 (CVE-2026-20316); the flaw is exploited, and chaining with the root-level bypass raises the stakes.
Fix
Apply Cisco's hot fixes, since there is no workaround, keep the FMC management interface off the public internet, and if the indicator appears, rotate all device credentials, keys, and certificates.

Russian actor exploits Outlook Web Access flaw for mailbox access that survives resets

Proofpoint reported a Russia-aligned group, tracked as Laundry Bear or TA488, exploiting a cross-site scripting flaw in on-premises Outlook Web Access to plant a stealthy backdoor. Tracked as CVE-2026-42897 and rated 8.1, it is a half-click exploit: opening a crafted email in OWA runs attacker JavaScript in the session. The implant, OWAReaper, steals OAuth tokens from mailbox add-ins and grants the low-privilege Default user Owner rights on every mail folder, so any account in the organization can read the mailbox. Because that grant lives on the Exchange server, rotating credentials and re-imaging the device do not remove the access. Microsoft flagged exploitation since May.

Check
Confirm on-premises Exchange has the fix for this flaw, then audit mailbox folder permissions for Owner rights wrongly granted to the Default user, and review add-ins with mailbox write access.
Affected
Organizations running on-premises Exchange Outlook Web Access (CVE-2026-42897); opening a crafted email runs attacker code, and the backdoor's server-side permission grant keeps access alive through credential resets and re-imaging.
Fix
Patch, then remove the malicious folder-permission grants and audit add-ins with mailbox write access, since patching alone does not evict the attacker, and hunt for OWAReaper artifacts and unusual token use.

Broadcom patches critical VMware flaws enabling VM escape and vCenter takeover

Broadcom released emergency patches for five VMware flaws, three of them critical, affecting ESXi, vCenter, Workstation, and Fusion. The most notable, CVE-2026-47876, is an out-of-bounds write in the ESXi VMXNET3 network adapter that lets an attacker with admin rights inside a guest virtual machine run code on the host, a VM escape. Two critical vCenter flaws follow: CVE-2026-59309 is an authentication bypass reachable over the network, and CVE-2026-59310, scored 9.8, allows code execution through a directory traversal. Broadcom warns the vCenter bypass could be chained with the escape or the code-execution flaw to seize the hypervisor without any guest foothold. No exploitation is reported yet.

Check
Apply the VMware fixes as an emergency change, since there are no workarounds, prioritizing vCenter and any ESXi hosts running virtual machines that use the VMXNET3 adapter.
Affected
Organizations running affected VMware ESXi, vCenter, Workstation, or Fusion (CVE-2026-47876, CVE-2026-59309, CVE-2026-59310); attackers can escape a VM to the host or bypass vCenter to compromise the hypervisor.
Fix
Upgrade to the fixed vCenter and ESXi builds Broadcom lists, restrict vCenter network access, and treat this as urgent, since attackers frequently target VMware after patches reveal the flaws.

Critical Rails flaw turns an image upload into a read of server secrets

The Ruby on Rails team disclosed a critical flaw in Active Storage that lets an unauthenticated attacker read arbitrary files by uploading a crafted image. Tracked as CVE-2026-66066 and scored 9.5, it affects applications that use the libvips image library and accept image uploads from untrusted users, which is the default in modern Rails. Active Storage passes uploads to libvips without disabling its unsafe image loaders, so a malicious file can read the server process environment, exposing the secret key base, database passwords, cloud storage keys, and API tokens. Those secrets can enable code execution and lateral movement. Rails is not aware of exploitation, and full details are held until August 28.

Check
Determine which Rails apps use Active Storage with libvips and accept untrusted image uploads, upgrade to the fixed releases, and ensure libvips is version 8.13 or newer.
Affected
Rails 7.0 through 8.1 applications using libvips Active Storage with untrusted image uploads (CVE-2026-66066); an unauthenticated upload can read server secrets, opening the door to code execution.
Fix
Upgrade Rails, update libvips to 8.13 or later, and rotate every secret the app can read, including the secret key base, master key, storage and database credentials, and third-party tokens.

Ruflo AI agent platform exposed 233 tools through an unauthenticated MCP bridge

Noma Labs found a critical flaw in Ruflo, an open-source platform for orchestrating swarms of AI agents that acts as a harness for coding agents like Claude Code and Codex. Tracked as CVE-2026-59726 and scored 10.0, the flaw is that Ruflo's default Docker deployment exposed its Model Context Protocol bridge to the network with no authentication, offering 233 callable tools. A single unauthenticated request could invoke a shell command tool to run code in the bridge container, read AI provider API keys, steal stored conversations, and poison the platform's persistent agent memory, which can steer future outputs even after the attacker leaves. The flaw is in Ruflo, not in the coding agents.

Check
If you run Ruflo, formerly Claude Flow, update to version 3.16.3 or later, and confirm its MCP bridge is not bound to a network-reachable interface.
Affected
Teams running Ruflo before 3.16.3 with the default Docker deployment (CVE-2026-59726); an unauthenticated network attacker can run commands, steal AI provider keys and conversations, and poison persistent agent memory.
Fix
Update Ruflo, rotate AI provider API keys, rebuild affected containers from clean images, inspect the agent memory store for unfamiliar instructions, and keep MCP bridges bound to loopback and behind authentication.

No-logs VPN breach exposes 58 million connection logs it promised not to keep

A breach at SplitVPN, a service formerly called NotVPN that marketed itself as keeping no logs, exposed a 17GB database containing roughly 58 million connection logs. The logs record which device connected to which server and when, running continuously up to the day of the breach, directly contradicting the no-logs promise. Cross-referenced with user and device tables holding emails, last-seen IP addresses, and hardware identifiers, they can reconstruct who connected from where and when for tens of millions of people. The data also includes about 23 million user records and 2.6 million payment records with masked card details. Operator account hashes were exposed too.

Check
SplitVPN or NotVPN users should assume their connection history and account details are exposed, change reused passwords, and watch for phishing and extortion referencing their VPN use.
Affected
Tens of millions of SplitVPN users whose connection logs, emails, IP addresses, device identifiers, and masked payment details were exposed, despite the service's advertised no-logs policy, enabling activity reconstruction and targeted fraud.
Fix
Treat no-logs claims as unverifiable marketing rather than a guarantee, prefer providers with independent audits or verifiable architectures, and where anonymity matters, avoid a single centralized intermediary that decides what to log.