Which versions of jscrambler are malicious?

The following npm versions of jscrambler are flagged malicious: 8.14.0, 8.16.0, 8.18.0, 8.20.0. Treat any of these as compromised.

How do I remediate jscrambler if I installed it?

jscrambler 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.

I already installed jscrambler — how do I know if it already compromised me?

If jscrambler 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.

Is jscrambler part of a known attack campaign?

Yes — jscrambler is associated with the IN-MAL-2026-009732, IN-MAL-2026-009733, IN-MAL-2026-009731, IN-MAL-2026-009734 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find jscrambler across my projects, lockfiles, and CI pipelines?

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

Malicious package

jscramblernpm

Malicious code in jscrambler (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10187

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall jscrambler

What this malware does

The package's main entry (dist/index.js) contains a top-level IIFE that runs on every require('jscrambler'). It reads a bundled 7.8 MB sibling file dist/intro.js, validates a custom container header (0x1b 0x43 0x53 0x49 0x01), selects a platform-specific gzip section (linux/win32/darwin), writes the decompressed bytes to os.tmpdir() under a hidden random dot-file name with mode 0755, and spawns the binary detached with stdio ignored and windowsHide, then unrefs the child. Errors are swallowed. The bundled payload dist/intro.js is not JavaScript: it uses a custom multi-platform container and contains strings characteristic of a cryptocurrency-wallet seed-phrase harvester and a browser-session stealer, including the BIP-39 English wordlist marker (bip39_english) and Chromium/BoringSSL TLS internals (ResumptionAttemptedWithVariedEms). Neither README nor CHANGELOG documents any native runtime component, and the CHANGELOG has no entries past 8.13.0. The wrapper's shape (custom magic header, hidden tmp filename, detached spawn, error-swallowed try/catch, undocumented payload) is inconsistent with the package's advertised CLI/API-client purpose and matches a malicious release / account-takeover pattern targeting installer wallets and browser sessions.

Malicious versions

4 flagged

8.14.08.16.08.18.08.20.0

Indicators of compromise (SHA-256)

4eb9f6bccdfcc1a1213b8e9d86149917ae76831117a5cb6b2ffb71fea91c1a8b

78072900cd02c14e3b48ce7a6b832ddd0deedb1d9bb0e90be7716f2fe69b8dfc

afb577cf150e98ebfe551df006c555204f327432baa3789473981888761a8677

fadc9262ceebc6743d3fb34251fb64ab6872d49fcc023596a27ef537a7928a20

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jscrambler (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jscrambler across your stack and pipelines.
If you installed it — respond
jscrambler 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 jscrambler 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 jscrambler 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. jscrambler on npm has been identified as a malicious package (versions 8.14.0, 8.16.0, 8.18.0, 8.20.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009732IN-MAL-2026-009733IN-MAL-2026-009731IN-MAL-2026-009734

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring