theta-sdk-js (npm) · Malicious Code
Affects theta-sdk-jsSource GCVE Database
Malicious package : remove theta-sdk-js and rotate any secrets on hosts that installed it.
Data as of 17 Jul 2026, 10:14 UTC
Malicious package
Published to npm · OSV MAL-2026-10135
What to do
Remove theta-sdk-js from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtheta-sdk-js | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6967c021e95228b33b18be4489fea5d404720cbd21beb53dac8bf7ea4f4d54d1) theta-sdk-js@1.2.15 ships src/decrypt.js and src/providers/BaseProvider.js which together implement a hidden execution channel. On module load, decrypt.js reads two encrypted blobs (rsa.db, des.db) from node_modules/tchain-api/apps/docs/app/, DES-decrypts them using the hardcoded password 'hydra' via crypto-js, and returns the plaintext. Top-level IIFEs in src/providers/BaseProvider.js spawn detached `node` child processes (`spawn('node', [], { detached: true, stdio: ['pipe','ignore','ignore'] })`), pipe the decrypted plaintext into stdin for execution, and call `unref()` so the child outlives the parent. The runtime dependency `tchain-api@^1.2.5` — declared in package.json — supplies the encrypted payload files, so `npm install theta-sdk-js` automatically stages the payload host. The distributed `dist/thetajs.cjs.js` (declared as `main`) is clean and does not contain this code; the dropper lives only in the src/ tree that is also shipped in the tarball, so consumers that import subpaths or use bundlers/tree-shakers that resolve src/index.js trigger the execution. Encrypting the payload in a sibling package with a hardcoded key, splitting the malicious code away from the declared entrypoint, and executing decoded plaintext in a detached child process are hallmarks of deliberate evasion, not legitimate SDK behavior. ## Source: ghsa-malware (338e0faee2d79bfcc4530b55cd8f077902060f62d23dbea70fc263438fc95e04) 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.
References
- npmjs.com/package/theta-sdk-js/v/1.2.16 (opens in a new tab)
- npmjs.com/package/theta-sdk-js/v/1.2.15 (opens in a new tab)
- npmjs.com/package/theta-sdk-js/v/1.2.14 (opens in a new tab)
- npmjs.com/package/theta-sdk-js/v/1.2.17 (opens in a new tab)
- github.com/advisories/GHSA-qj2r-27rj-cc82 (opens in a new tab)