Which versions of encrata-cli are malicious?

The following npm versions of encrata-cli are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate encrata-cli if I installed it?

encrata-cli 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 encrata-cli — how do I know if it already compromised me?

If encrata-cli 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 encrata-cli part of a known attack campaign?

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

Malicious package

encrata-clinpm

Malicious code in encrata-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4551

Immediate action

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

npm uninstall encrata-cli

What this malware does

package.json declares "postinstall": "node install.js", which runs at install time. install.js requires both child_process and https, branches on process.platform to enumerate host details, and issues an outbound https.get(...) carrying the collected data. This is the canonical install-time system-information exfiltration shape: child_process to spawn host-info commands, platform-gated logic to pick the right binary per OS, and HTTPS egress to ship the result. There is no legitimate reason for a CLI's postinstall to gather host metadata and POST/GET it off-host. Installing this package on any machine (developer laptop, CI runner, build server) discloses host details to a remote endpoint and provides an install-time code-execution surface.

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

80b70f02e409ec9eb28e4ddcdf37d477f4ffe774ff0a4026f0e242dcc0a1ef48

8a7070dd3d284cb91d046f6be633445a29af8e30a4fc0d3c77dce18bf847c0b0

b4eea8e53244b7114760ece8c8842f1936baca2e93ba8f49c76f7d02e7f0ffb6

e98813f52fa8e9fc3c04bffd023445dbfed4a9b405d1e3f85511673f5e86dce7

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 encrata-cli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging encrata-cli across your stack and pipelines.
If you installed it — respond
encrata-cli 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 encrata-cli 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 encrata-cli 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. encrata-cli on npm has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004147IN-MAL-2026-004146IN-MAL-2026-003529IN-MAL-2026-003528

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks encrata-cli-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