Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

chain-sdk-jsnpm

chain-sdk-js is a confirmed malicious npm package (MAL-2026-10608) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3, 1.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in chain-sdk-js (npm)

MAL-2026-10608
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall chain-sdk-js

What this malware does

chain-sdk-js is a typosquat of @thetalabs/theta-js (package name, description, author 'Theta Labs', and bundle filenames thetajs.cjs.js/thetajs.umd.js all mimic the legitimate SDK). The package's main entry, executed on require/import in cjs, esm, and umd builds, DES-decrypts an opaque blob (rsa.db) loaded from the co-installed dependency thedata (^1.0.1) using the hardcoded password 'hydra', then spawns a node child process and pipes the decrypted bytes into its stdin for execution (child_process.spawn('node', [], {...}); rsa_exec.stdin.write(String(rsaDecrypted))). Splitting the loader from the encrypted payload into a separately-published dependency (node_modules/thedata/apps/docs/app/rsa.db and des.db) hides the actual code that runs from static inspection of this tarball. The dist bundles also contain hardcoded POST/fetch call sites consistent with outbound network activity from the executed payload. Any consumer that installs and imports this package runs attacker-controlled code with the installer's privileges; the typosquat targets Theta blockchain developers who handle wallet and private-key material.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

5 flagged
1.0.21.0.31.0.41.0.51.0.6

Indicators of compromise (SHA-256)

26a55087b41c67e97ba4392519ae3253cea57d313c7771503c769a0effcfcf59
c146b995e5fb482788fa27363ed4e24c2bf890559e6d8eeb191eedcd458609de
4f4206ecba994ddf63140b58c931d293591dfa1726d61d915b53429ff948812e
cb94ce743d92fe81015db70380ba325e78e4271b78689a9a6998cda4e6bdc038
69ba71d312938a71cb0153fdd3f7aedd5c9f8a7c90d156c6768775518c77b416
f713f26f148a489ba3a8a242faf3bcb4963cd513eb94c02a74d2877f92fc162a

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chain-sdk-js (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chain-sdk-js across your stack and pipelines.

  2. If you installed it — respond

    chain-sdk-js 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.

  3. Did it already run?

    If chain-sdk-js 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.

  4. How O3 protects you

    O3 blocks chain-sdk-js 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

No. chain-sdk-js on npm has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010538IN-MAL-2026-010532IN-MAL-2026-010533IN-MAL-2026-010560IN-MAL-2026-010710GHSA-2p8p-vrrr-9f6c

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks chain-sdk-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

chain-sdk-js (npm) malicious package — MAL-2026-10608 | O3 Security