Loading story…
CISA added three actively exploited software supply-chain vulnerabilities to its Known Exploited Vulnerabilities catalog: CVE-2026-48027 in Nx Console, CVE-2026-45321 in TanStack npm packages, and CVE-2026-8398 in DAEMON Tools Lite. The Nx Console incident involved a malicious 18.95.0 extension published to Visual Studio Marketplace and OpenVSX after a prior compromise of Nx developer systems; CISA said the poisoned extension was automatically distributed and was used to compromise a GitHub employee device, leading to unauthorized access to and exfiltration of internal GitHub repositories. CISA identified Nx Console 18.100.0 as clean and said federal agencies must remediate the listed flaws under BOD 22-01 or discontinue use if mitigations are unavailable.
CISA also warned that the TanStack intrusion abused GitHub Actions through a pull_request_target misconfiguration, cache poisoning, and OIDC token theft to publish malicious packages, with reporting indicating 84 malicious versions across 42 packages carried valid Sigstore/SLSA provenance. In parallel, the agency highlighted the Megalodon campaign, in which attackers inserted malicious GitHub Actions workflows into public repositories to steal CI/CD secrets, cloud credentials, and tokens, and said organizations should audit workflow files and contributor activity, revert unauthorized automated-account changes, conduct forensic reviews, rotate potentially exposed secrets, delay package pulls, pin trusted versions, and use only trusted package sources. The DAEMON Tools Lite case involved trojanized signed installers reportedly distributed from the vendor’s website after a suspected compromise of build or distribution systems.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
7 events from the most recent confirmed update back to the earliest known activity.
Reporting on the KEV additions states that Federal Civilian Executive Branch agencies were required under BOD 22-01 to remediate the newly listed vulnerabilities by a set deadline. One source gives the deadline as June 10, 2026, while another reports June 17, 2026.
CISA published an alert warning about emerging software supply-chain intrusion campaigns affecting developer ecosystems, including the Nx Console compromise and the Megalodon GitHub workflow campaign. The agency urged organizations to audit workflows and contributor activity, conduct forensic reviews, rotate exposed secrets, and use trusted package sources.
Following a prior compromise of Nx developer systems, the malicious Nx Console extension was automatically distributed and used to compromise a GitHub employee device. Attackers then gained unauthorized access to and exfiltrated internal GitHub repositories.
CISA updated its Known Exploited Vulnerabilities Catalog to add CVE-2026-48027, CVE-2026-45321, and CVE-2026-8398, covering the Nx Console, TanStack, and DAEMON Tools Lite supply-chain incidents. The update raised the catalog total from 1,603 to 1,606 vulnerabilities.
A poisoned Nx Console Visual Studio Code extension, version 18.95.0, was briefly published to the Visual Studio Marketplace and OpenVSX. The malicious release was later assigned CVE-2026-48027.
CISA warned organizations to review and revert unauthorized automated-account changes made especially after May 18, 2026, in connection with the Megalodon campaign. The campaign involved malicious GitHub Action workflows injected into public repositories to steal CI/CD secrets, cloud credentials, and tokens.
Praetorian published research describing GitHub Actions exploitation techniques involving pull_request_target and related workflow abuse. Later reporting on the TanStack compromise references these methods as part of the attack chain.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
7 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcesecurityaffairs.com
Open sourcethecyberthrone.in
Open sourcecisa.gov
Open sourcecisa.gov
Open sourcegithub.com
Open sourcepraetorian.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Attackers compromised TanStack’s npm release pipeline and published 84 malicious versions across 42 `@tanstack/*` packages, an incident tracked as **CVE-2026-45321** with a CVSS score of 9.6. The intrusion chained a vulnerable GitHub Actions `pull_request_target` workflow, cache poisoning across the fork-to-base trust boundary, and theft of an OIDC token from runner memory, allowing the adversary to push malware under a trusted identity. The poisoned releases carried valid **SLSA Build Level 3** provenance, showing that the builds originated from the legitimate pipeline even though that pipeline had been subverted. The malicious packages used npm lifecycle execution and injected components including a fake `@tanstack/setup` dependency and a payload file named `router_init.js` to exfiltrate secrets from CI/CD systems and developer machines. Reporting tied the activity to the **Shai-Hulud** malware family and described a two-stage payload that harvested credentials, scraped GitHub Actions runner memory, exfiltrated data through multiple channels, and attempted self-propagation with stolen maintainer tokens; related package abuse was also noted in ecosystems including `@opensearch-project/opensearch`, `@uipath/*`, and `@redhat-cloud-services`. Defenders were urged to treat any affected installation as a likely credential compromise and to hunt for signs such as unusual publication bursts, tarball differences, unexpected `github:` dependencies pinned to commit SHAs, and files present in published tarballs but absent from package allowlists.
Jul 10, 2026
A large software supply-chain campaign dubbed **Mini Shai-Hulud** compromised more than 170 npm packages and at least two PyPI packages tied to projects including **TanStack, Mistral AI, OpenSearch, UiPath, Guardrails AI,** and others. Researchers and vendors attributed the activity to **TeamPCP**, saying the attackers abused GitHub Actions release workflows—especially `pull_request_target`, cache poisoning, and theft of short-lived **OIDC** material from runners—to publish trojanized packages with apparently legitimate **SLSA** provenance, Sigstore attestations, and trusted-publishing signatures. Reports variously counted between roughly 160 and 400+ malicious package versions, with some affected packages totaling hundreds of millions of downloads, and OpenSearch and Mistral both confirmed compromised releases while TanStack described a chained workflow attack on its publishing pipeline. The malware targeted developer workstations and CI/CD systems, stealing **npm**, **GitHub**, cloud, Kubernetes, Vault, SSH, Docker, and AI-tool credentials, then attempting worm-like propagation by republishing infected packages with stolen tokens or workflow-issued publish credentials. Investigators said the payload also established persistence through **VS Code** tasks, **Claude Code** hooks, and in some cases system services, while exfiltrating data through **Session**, GitHub dead drops, and other attacker infrastructure; some variants included extortion notes, dead-man-switch logic, and geofenced destructive behavior. Defenders were urged to treat hosts that installed affected versions as potentially fully compromised, remove persistence before revoking tokens where applicable, rotate all exposed secrets from clean systems, invalidate CI caches, audit lockfiles and publishing activity, and rebuild impacted environments from trusted sources.
Jul 12, 2026
Security researchers reported multiple **software supply chain** threats targeting developers via public package ecosystems. Tenable analyzed a malicious npm package, **`ambar-src`**, that reached roughly **50,000 downloads** in days before removal; it executed during installation via **malicious `preinstall` behavior**, used evasion techniques, and dropped OS-specific payloads for Windows, Linux, and macOS, with typosquatting assessed as the likely lure (mimicking *`ember-source`*). Separate reporting described a campaign using **malicious NuGet packages** (e.g., **NCryptYo**, **DOMOAuth2_**, **IRAOAuth2.0**, **SimpleWriter_**) that impersonated legitimate .NET libraries, executed code on assembly load, and established local proxying/backdoor behavior to facilitate credential theft and persistence in ASP.NET environments. Additional coverage warned of an npm “worm-like” propagation pattern impacting **CI pipelines and AI coding tools**, reinforcing that developer tooling and build systems are high-risk choke points where a single poisoned dependency can spread quickly across environments. While the broader set of articles also included unrelated breach, ransomware, and policy items, the developer-focused supply chain reporting consistently emphasized that **installation-time execution** and **typosquatting/impersonation** enable compromise even when developers never directly call the malicious code, and that traditional detection can lag (e.g., low initial antivirus detection rates for obfuscated .NET payloads).
Jun 29, 2026