Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7

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.

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.

Compromised joyfill npm packages run a remote access trojan when imported

Attackers published malicious versions of the @joyfill/components and @joyfill/layouts npm packages that run a remote access trojan as soon as the package is imported, not merely installed. Because the payload executes at import time, defenses that block install scripts, such as installing with scripts disabled, do not stop it. The malicious code sat only in the published tarballs with no matching source change, pointing to a registry or publishing pipeline compromise. Once loaded, it profiles the host, opens a remote-control channel, and can run shell commands, upload files, read the clipboard, and tamper with developer tools, using blockchain networks to resolve its next payload for resilience.

Check
Check whether any project, CI runner, or build imported the malicious @joyfill/components or @joyfill/layouts versions, focusing on import-time execution rather than only install scripts.
Affected
Developers and CI pipelines that imported the compromised joyfill packages; the trojan runs in any process that loads them, giving attackers remote control and access to developer credentials and tools.
Fix
Remove the malicious versions, pin known-good releases, rebuild from clean state, rotate secrets reachable from affected machines, and add runtime and egress monitoring, since install-script controls do not catch import-time payloads.

Security scanners can be turned into a foothold for supply chain attacks

New research shows that application security scanners embedded in the software pipeline can themselves be attacked, because analyzing a repository is not always a read-only action. Many scanners execute code or process files in ways that can be forced to run attacker content when it is handled without isolation. For example, a tool that scans cloud configuration files against a folder of custom rules can be fed a rule that is actually a malicious program, which the scanner runs when it loads it. Since scanners often hold broad access to source, secrets, and build systems, a compromised one is a strong pivot point into the wider environment.

Check
Review how your code and configuration scanners handle untrusted repository content, and check whether they execute rules, plugins, or files without sandboxing and multi-tenant isolation.
Affected
Teams whose security scanners process untrusted repository content without isolation; an attacker controlling a scanned repo can plant content that runs code inside the scanner, which often holds broad access to secrets.
Fix
Run scanners in isolated, least-privilege sandboxes, treat all scanned content as untrusted input, enforce multi-tenancy separation, and limit the source, secrets, and build access that scanning environments hold.