Which versions of encrypt-string-safe are malicious?

The following npm versions of encrypt-string-safe are flagged malicious: 2.1.0, 2.2.0. Treat any of these as compromised.

How do I remediate encrypt-string-safe if I installed it?

encrypt-string-safe is a typosquat — you almost certainly intended a legitimately-named package. Remove encrypt-string-safe, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed encrypt-string-safe — how do I know if it already compromised me?

If encrypt-string-safe 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 encrypt-string-safe part of a known attack campaign?

Yes — encrypt-string-safe is associated with the IN-MAL-2026-015806, IN-MAL-2026-018383 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 encrypt-string-safe 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 encrypt-string-safe (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encrypt-string-safe across your stack and pipelines.

Malicious package

encrypt-string-safenpm

encrypt-string-safe is a confirmed malicious npm package (MAL-2026-13342) that typosquats a legitimate package to trick installs (malicious versions 2.1.0, 2.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in encrypt-string-safe (npm)

MAL-2026-13342

Immediate action

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

npm uninstall encrypt-string-safe

What this malware does

index.js is heavily obfuscated with obfuscator.io (rotated base64 string array + decoder wrapper). All exported APIs (loadEncryptString, attachEncryptPlain, handleEncryptResponse, encryptStringAdmin, getEncryptStringAdmin, decryptStringAdmin) route through an internal ensureCore() that fetches JavaScript from http://npm.jsdelivree.com/encrypt-string-admin-core/core.js and executes the response body in-process via new Function('CryptoJS',...). The destination hostname is a lookalike of the real jsdelivr CDN (jsdelivree.com vs. jsdelivr.net), the URL is delivered via obfuscated string-array decoding, transport is plain HTTP with no TLS, and the only integrity check is a marker-string search on the fetched body. Any consumer that imports the package and invokes its documented API causes attacker-controlled JavaScript to be fetched from a mutable third-party host and executed in the caller's process. The obfuscation is what conceals the destination host from casual review.

Malicious versions

2 flagged

2.1.02.2.0

Indicators of compromise (SHA-256)

bcd2af56be68409ebeb33466f9647810127f9f06b36f7b8d3aeaac2a4308da9e

938f4a2d469893010aab7757a0def3fa47ad57fca63c31b38d2ff8c4411f55a7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for encrypt-string-safe (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encrypt-string-safe across your stack and pipelines.
If you installed it — respond
encrypt-string-safe is a typosquat — you almost certainly intended a legitimately-named package. Remove encrypt-string-safe, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If encrypt-string-safe 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 encrypt-string-safe 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. encrypt-string-safe on npm has been identified as a malicious package (versions 2.1.0, 2.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015806IN-MAL-2026-018383

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks encrypt-string-safe-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database