Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7

Self-spreading npm worm ChainDrop poisons over 1,300 package versions in hours

A self-propagating worm named ChainDrop tore through the npm registry on August 4, poisoning packages that huge parts of the software world depend on. It began by hijacking the GitHub account behind keyv, a caching library pulled in about 150 million times a week, then spread to sibling and downstream packages, reaching over 1,300 poisoned versions with billions of monthly downloads within hours. A preinstall script harvests credentials from developer and continuous integration environments, including AI agent tokens, cloud keys, and self-hosted CI secrets, then uses stolen npm publishing access to poison more packages. A descendant of the earlier Shai-Hulud worm, it even forged valid-looking build provenance.

Check
Compare lockfiles and resolved versions against the published affected-package list, and treat any machine that installed a poisoned version as compromised, but remove the malware's token watcher before rotating anything.
Affected
Developers and CI systems that installed a poisoned version during the attack window; the worm steals repository, registry, cloud, AI agent, and private-key credentials, then self-spreads through npm publishing access.
Fix
Rotate all reachable credentials after removing the token watcher, install with scripts disabled, pin and delay adoption of new versions, and check for injected hooks in developer tooling and continuous integration configuration.

77 malicious Open VSX extensions posed as dev tools to harvest developer data

Manifold Security found 77 malicious extensions on Open VSX, the open marketplace that editors like VSCodium, Cursor, and Windsurf pull extensions from, impersonating legitimate developer tools. Detected between July 26 and August 1, all 77 were linked through a shared exfiltration domain and common code. Fifty-eight sent only basic system information, while the other 19 performed deeper reconnaissance, exfiltrating developer, Git repository, and continuous integration metadata. Manifold found no access to source code, credentials, tokens, or SSH material and did not determine the campaign's goal. The extensions were pulled from Open VSX by August 3, but must still be removed manually from affected machines.

Check
Check developer machines and workspace configuration files for the extension identifiers in Manifold's report, remove any that appear, and block the campaign's exfiltration domain, mangorbit dot com.
Affected
Developers who installed the evil-twin extensions from Open VSX through editors like VSCodium, Cursor, or Windsurf; the extensions leaked system, Git repository, and continuous integration metadata about their environments.
Fix
Vet extensions and publishers before installing, prefer verified sources, inventory installed extensions across developer machines, block the known exfiltration domain, and monitor for extensions contacting unexpected external hosts.

XCSSET returns to infect Macs when developers build poisoned Xcode projects

Palo Alto Networks Unit 42 detailed a rebuilt version of XCSSET, macOS malware that spreads through Xcode developer projects. The actors compromise Git repositories and inject a downloader into ordinary files inside a project, so that when a developer builds the cloned project, a hidden loader runs under their own account with no permission prompt. It then infects every other Xcode project on the machine and propagates through shared code. Version 40 hides its logic in memory, generates polymorphic payloads, and adds a Chrome hijacker that drives the browser through its debugging protocol plus a component that trojanizes Telegram. Seventeen modules handle credential, keystroke, clipboard, and browser theft.

Check
Inspect Xcode projects, especially shared or cloned ones, for unexpected build scripts or run phases before building them, and watch developer machines for Chrome launched with debugging enabled.
Affected
macOS developers who build Xcode projects cloned from Git repositories; a hidden loader runs at build time under the developer's account, spreads to other local projects, and steals credentials and browser data.
Fix
Review third-party Xcode projects before building, build untrusted ones in isolated environments, keep macOS and tools patched, and monitor for browsers launched with remote debugging and unexpected outbound connections.

Pass-ta-key attacks let malware on a PC steal and export Google-synced passkeys

Palo Alto Networks Unit 42 described three techniques, collectively Pass-ta-key, in which malware already running on a compromised Windows PC abuses Google Password Manager's synced passkeys. None break the underlying cryptography; they target how Chrome stores device keys, re-enrolls a device, and whether a site verifies that a person was present. The techniques can silently obtain a valid login assertion without any unlock prompt, register an attacker-controlled verification key that defeats user-verification checks, or extract the secret that decrypts all of a user's synced passkeys for reuse elsewhere. Passkeys still resist phishing, but a fully compromised endpoint undermines the synced-passkey model.

Check
Recognize that endpoint compromise, not phishing, is the threat to synced passkeys, and confirm your important services actually require and validate the user-verification flag on passkey logins.
Affected
Users of Google Password Manager synced passkeys in Chrome on Windows whose device is infected; malware can forge logins, bypass user verification, and export all synced passkeys, even for strict accounts.
Fix
Prioritize endpoint security since these attacks need local malware, require and strictly validate user verification on sensitive accounts, and consider hardware-bound passkeys or security keys rather than synced ones for high-value access.

Malicious npm packages split a RAT across files to slip past code review

Researchers at Socket found 18 malicious npm packages that deliver a cross-platform remote access trojan to users of Alibaba developer tools, splitting the attack across many packages so each looks harmless on its own. Ten lure packages with no real function depend on a bridge package, which pulls in loaders that fetch a rule-engine configuration from GitHub and use it to run OS-specific payloads from a server disguised as Alibaba infrastructure. On Windows it even replaces a legitimate Alibaba security app with a trojanized copy. The final trojan can steal data, run commands, and move laterally, and the campaign stayed hidden for about three months.

Check
Analyze dependency trees as a whole rather than one package at a time, since this campaign hid its logic across lure, bridge, and loader packages that each look benign in isolation.
Affected
Developers using Alibaba tooling who installed the malicious packages; the fragmented loader assembles a remote access trojan that steals data, runs commands, and moves laterally, evading per-package review.
Fix
Vet dependencies and their transitive graph, watch for packages that only pull in others or fetch configuration from external repositories, pin trusted versions, and monitor developer machines for unexpected outbound connections.

INC ransomware becomes the main group exploiting SonicWall VPN appliances

Resecurity reports that the INC ransomware operation has become the dominant group exploiting two SonicWall SMA1000 VPN appliance flaws, accelerating its attacks since early August. The pair, CVE-2026-15409 and CVE-2026-15410, were exploited as zero-days before SonicWall patched them in mid-July, and can be chained to gain root on the appliance and extract credentials, session databases, and one-time-password data. Many appliances remain unpatched or already compromised, leaving footholds attackers can reuse. Victims listed recently span private and government organizations across several countries, and some reported follow-up emails and phone calls from people claiming to help with the ransomware.

Check
Confirm SonicWall SMA1000 appliances have the mid-July fixes, and because pre-patch exploitation was common, run a compromise assessment and rotate credentials, sessions, and one-time-password secrets the appliance handled.
Affected
Organizations running SonicWall SMA1000 appliances (CVE-2026-15409, CVE-2026-15410); INC ransomware is actively chaining the flaws to root devices, and unpatched or already-compromised appliances remain reusable footholds.
Fix
Patch, then re-image compromised appliances and reset all credentials and one-time-password tokens they processed, restrict management access, and treat unsolicited offers of ransomware help as part of the extortion.

Poisoned Adform ad script swapped crypto wallet addresses on customer sites

Attackers compromised a widely used tracking script from advertising firm Adform, turning it into a browser-side tool that rewrites cryptocurrency wallet addresses. The malicious code was appended in obfuscated form to Adform's trackpoint-async.js library, served from the company's own infrastructure, so any site loading it ran the altered script in visitors' browsers. It swapped Bitcoin, Ethereum, and Tron addresses both in the clipboard and in form fields, redirecting transfers to the attacker. Adform detected and removed the code on July 27 and says it did not install software or persist after a page closed, but cached copies may linger. It has not said how many page loads were affected.

Check
Warn people who sent cryptocurrency after visiting sites recently to clear their browser cache and verify every wallet address, and review whether your own sites embed third-party scripts that could be poisoned.
Affected
Anyone who copied or entered a crypto wallet address on a site loading Adform's tracking script on July 27; the swapped address silently redirected funds, and cached copies may still be active.
Fix
Limit and monitor third-party scripts, use subresource integrity where possible, isolate payment and wallet pages from ad and tracking code, and treat any shared external script as a single point of compromise.

Arch Linux halts package adoptions after infostealer floods the user repository

The Arch Linux project temporarily disabled adoption of packages in its user repository, the AUR, after a wave of malicious takeovers of existing packages. Attackers seized packages through compromised maintainer accounts or by adopting orphaned ones, then shipped a Rust-based infostealer that grabs browser credentials, cryptocurrency wallets, password manager data, cloud and developer secrets, AI service API keys, and SSH keys. It also opens remote command execution over an encrypted Tor channel and spreads to other machines using stolen SSH keys. A researcher tracking the campaign claims more than 200 packages were hit, including some popular ones, though that list is not independently confirmed.

Check
If you use the AUR, review recently installed or updated packages and their maintainers, inspect build files before installing, and rotate SSH keys and secrets if you ran a suspect package.
Affected
Arch Linux users who install from the AUR; a hijacked or adopted package can run a Rust infostealer that harvests developer, cloud, and AI credentials and SSH keys, then self-spreads.
Fix
Read AUR build scripts before installing, prefer well-maintained packages, rotate exposed credentials and SSH keys, watch for outbound Tor connections, and treat orphaned or newly adopted packages with particular caution.

Attacker wires DeepSeek into an agent to hunt and exploit exposed servers

Palo Alto Networks Unit 42 detailed a Chinese-speaking attacker who used the DeepSeek model as the reasoning engine inside an open-source agent called Hermes to attack exposed servers with little human input. Taking instructions over Telegram and using an internet asset search engine, the agent ran in a mode that executes commands without asking permission: from a single task, it downloaded a public exploit, enumerated vulnerable Langflow and n8n instances, judged targets by value, and attempted exploitation on its own. The autonomous attempts failed, blocked by authentication and configuration, though the operator succeeded manually elsewhere. The operation was exposed when the agent accidentally served its own working directory over the web.

Check
Keep self-hosted tools like n8n and Langflow patched, authenticated, and off the public internet, since autonomous agents now scan asset search engines and attempt exploitation without a human in the loop.
Affected
Organizations exposing self-hosted AI and automation tools such as Langflow and n8n; autonomous AI agents can discover, rank, and attack them at scale, though basic authentication and hardening blocked the observed attempts.
Fix
Require authentication, disable risky auto-login options, restrict management interfaces, and patch known flaws, since the defensive configurations that stopped this agent are the same controls that blunt automated exploitation generally.

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.