8 matches found
are-you-get-tanstack-attack
TanStack Router CVE Scanner A security scanning tool to detect the TanStack Router CVE | TanStack Router GHSA in your projects. Overview This tool scans your codebase for indicators of the TanStack Router vulnerability CVE-2026-45321 / GHSA-g7cv-rxg3-hmpx, which affects specific versions of...
tanstack-compromise-checker
tanstack-compromise-checker ⚠️ Disclaimer: This tool was built for my own use case. All indicators are derived from the following advisory sources: GHSA-g7cv-rxg3-hmpx Snyk: TanStack npm packages compromised StepSecurity: Mini Shai-Hulud deep dive If new IOCs, payload variants, or attacker...
mini-shai-hulud-detector
Mini Shai-Hulud Detector One-command scanner for the Mini Shai-Hulud npm supply-chain attack CVE-2026-45321, CVSS 9.6. Critical: detect before rotating tokens The worm installs a persistence daemon gh-token-monitor that runs rm -rf if it detects credential revocation. Do not rotate your GitHub PA...
scan-shai-hulud
scan-shai-hulud A fast, zero-dependency Bash scanner to detect whether your machine is affected by the CVE-2026-45321 "Mini Shai-Hulud" supply chain attack. On May 11, 2026, over 170 npm packages and 2 PyPI packages across TanStack, Mistral AI, UiPath, OpenSearch, and Guardrails AI were...
VulnCheck KEV: CVE-2026-45321
TanStack contains an unspecified vulnerability that allowed malicious versions of the product to be published to the npm registry to publish credential-stealing malware under a trusted identity...
Exploit for Embedded Malicious Code in Tanstack Tanstack\/Arktype-Adapter
Simulasi Supply Chain Attack — CVE-2026-45321 TanStack Ed...
CVE-2026-45321
creationtimestamp| type| source ---|---|--- 2026-05-12 12:20:35+00:00| seen| https://bsky.app/profile/dameyiwu.bsky.social/post/3mlnrlvzty22x 2026-05-12 15:00:07+00:00| seen| Telegram/88YkBdmMMIAUjkN-cy3WAm2Yboedxaf0GfTYOA3KafU0qTc 2026-05-12 18:40:06+00:00| seen| https://t.me/truesecator/8195...
CVE-2026-45321
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...