@kuperka/chainguard-sdknpm
@kuperka/chainguard-sdk is a confirmed malicious npm package (MAL-2026-13688) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @kuperka/chainguard-sdk (npm)
What this malware does
Package @kuperka/[email protected] exposes a single payload, window.VEIL.init(), that on load harvests document.cookie, every localStorage/sessionStorage entry, all form input values, meta CSRF/auth tokens, and Web3 wallet identifiers (window.ethereum, window.solana), base64-encodes the blob, and transmits it to the hardcoded endpoint https://webhook.site/b9155136-5f6d-4084-b19e-33c694a44616 via both Image().src GET and fetch POST. It additionally scans document.documentElement.outerHTML with credential-shaped regexes for Stripe live keys (sk_live_), AWS access keys (AKIA), GitHub personal access tokens (ghp_), JWTs, and OpenAI keys (sk-), including any matches in the exfil payload. A capturing keydown listener buffers keystrokes typed into any INPUT/TEXTAREA/SELECT along with field context (name/id/placeholder) and periodically posts them to the same endpoint. window.fetch is monkey-patched to record every outbound URL, method, Authorization header, and up to 2000 bytes of request body, forwarding captured bearer tokens and request bodies to the same webhook. After exfiltration the code renders a full-viewport overlay branded 'ChainGuard SECURITY & SIMULATION ENGINE' displaying scripted 'Initializing/Fetching/Simulating/Sandbox emulation complete' log lines and a hardcoded 'Overall Risk Score: 0 / No Threats Detected' result, concealing the theft from the user. The package name and 'chainguard' branding impersonate a legitimate security tool.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @kuperka/chainguard-sdk (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @kuperka/chainguard-sdk across your stack and pipelines.
If you installed it — respond
@kuperka/chainguard-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @kuperka/chainguard-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @kuperka/chainguard-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @kuperka/chainguard-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.