encryptstringadminnpm
encryptstringadmin is a confirmed malicious npm package (MAL-2026-11012) that executes malicious code on install (malicious versions 1.2.1, 1.3.0, 1.4.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in encryptstringadmin (npm)
What this malware does
index.js is a heavily obfuscated loader (rotated string-array decoder, control-flow flattening, self-defending/console-tamper stubs, debug-protection loop) whose only real behavior is a runtime fetch-and-eval. When any exported API (loadEncryptString/encryptStringAdmin/etc.) is invoked, the module fetches JavaScript text from cdn.jsdelivr.net/npm/encryptstringadmincore/ with cache: 'no-store' and a cache-busting query parameter _esa=Date.now(), then executes the response body in the consumer's process via new Function('CryptoJS', text +...)(CryptoJS). The URL is not version-pinned, no integrity check or signature verification is performed, and the cache-busting parameter defeats any caching layer, so the package author (or anyone able to publish to that CDN path) can change the executed bytes at any time. The mismatch between the trivial loader logic and the heavy obfuscation used to hide it is consistent with deliberate evasion of static review.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for encryptstringadmin (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encryptstringadmin across your stack and pipelines.
If you installed it — respond
Remove encryptstringadmin from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If encryptstringadmin 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 encryptstringadmin 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 encryptstringadmin-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.