CVE-2026-45321: CWE-506: Embedded Malicious Code in @tanstack arktype-adapter
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
AI Analysis
Technical Summary
On May 11, 2026, an attacker published 84 malicious package versions across 42 @tanstack npm packages, including arktype-adapter, by abusing GitHub Actions OIDC trusted-publisher bindings. The attack chain involved a pull_request_target misconfiguration allowing code execution, cache poisoning crossing fork-to-base trust boundaries, and runtime memory extraction of OIDC tokens from the Actions runner. This enabled the attacker to publish credential-stealing malware under legitimate publisher credentials without modifying the publish workflow itself. Each affected package received exactly two malicious versions published minutes apart. The vulnerability is tracked as CVE-2026-45321 with a CVSS 3.1 score of 9.6 (critical). No patch or official remediation has been disclosed.
Potential Impact
The vulnerability allows an attacker to publish malicious versions of trusted npm packages under legitimate publisher credentials, potentially distributing credential-stealing malware to users who install these packages. This compromises confidentiality, integrity, and availability of affected systems. The attack leverages weaknesses in CI/CD pipeline configurations and token handling, undermining trust in the software supply chain. No known exploits in the wild have been reported so far.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using the affected versions (1.166.12 and 1.166.15) of the @tanstack arktype-adapter and related packages. Review and harden GitHub Actions workflows to prevent pull_request_target misconfigurations and cache poisoning. Monitor for updates from the @tanstack project and npm registry regarding patched versions or further mitigation steps.
CVE-2026-45321: CWE-506: Embedded Malicious Code in @tanstack arktype-adapter
Description
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
CVSS v3.1
Score 9.6critical
Affected software
pkg:npm/@tanstack/arktype-adapterRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
On May 11, 2026, an attacker published 84 malicious package versions across 42 @tanstack npm packages, including arktype-adapter, by abusing GitHub Actions OIDC trusted-publisher bindings. The attack chain involved a pull_request_target misconfiguration allowing code execution, cache poisoning crossing fork-to-base trust boundaries, and runtime memory extraction of OIDC tokens from the Actions runner. This enabled the attacker to publish credential-stealing malware under legitimate publisher credentials without modifying the publish workflow itself. Each affected package received exactly two malicious versions published minutes apart. The vulnerability is tracked as CVE-2026-45321 with a CVSS 3.1 score of 9.6 (critical). No patch or official remediation has been disclosed.
Potential Impact
The vulnerability allows an attacker to publish malicious versions of trusted npm packages under legitimate publisher credentials, potentially distributing credential-stealing malware to users who install these packages. This compromises confidentiality, integrity, and availability of affected systems. The attack leverages weaknesses in CI/CD pipeline configurations and token handling, undermining trust in the software supply chain. No known exploits in the wild have been reported so far.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid using the affected versions (1.166.12 and 1.166.15) of the @tanstack arktype-adapter and related packages. Review and harden GitHub Actions workflows to prevent pull_request_target misconfigurations and cache poisoning. Monitor for updates from the @tanstack project and npm registry regarding patched versions or further mitigation steps.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-11T20:50:30.539Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a028743cbff5d86108b505d
Added to database: 05/12/2026, 01:49:55 UTC
Last enriched: 06/02/2026, 21:06:56 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 309
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.