Which versions of zenntechinc-cli are malicious?

The following npm versions of zenntechinc-cli are flagged malicious: 1.6.4, 1.6.6. Treat any of these as compromised.

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

zenntechinc-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed zenntechinc-cli — how do I know if it already compromised me?

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

Yes — zenntechinc-cli is associated with the IN-MAL-2026-018760, IN-MAL-2026-018759 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 zenntechinc-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 zenntechinc-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 zenntechinc-cli across your stack and pipelines.

Malicious package

zenntechinc-clinpm

zenntechinc-cli is a confirmed malicious npm package (MAL-2026-14539) that opens a backdoor for remote access (malicious versions 1.6.4, 1.6.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zenntechinc-cli (npm)

MAL-2026-14539

Immediate action

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

npm uninstall zenntechinc-cli

What this malware does

The npm package ships an obfuscated payload appended to templates/backend/.eslintrc.js, after a legitimate-looking ESLint config. The payload uses obfuscator.io-style string-array indirection (rotating _0x12f0() table, hex-named identifiers) to conceal Ethereum JSON-RPC endpoints (eth.drpc.org, ethereum.publicnode.com, blastapi.io, blockscout) and an Etherscan-style txlist indexer path. It queries the latest transaction from a hardcoded sender address (0xa322e5f3...9adc2490ef), decodes two IPv4 C2 addresses from the transaction's to field, fetches an XOR-encoded payload from those IPs, and executes it via eval() and spawn('node', ['-e', payload], {detached:true}).unref(). The CLI's new subcommand in bin/zenntechinc.js recursively copies the entire templates/backend tree — including the malicious.eslintrc.js — into the user-specified target directory via copyDirectory(), with no filtering. Any subsequent editor open, ESLint invocation, or lint script run inside the generated project loads this.eslintrc.js and triggers the blockchain-resolved remote code execution with full developer privileges. The CLI's advertised purpose (backend scaffolding) is the delivery vector for the RCE payload into the installer's workspace.

Malicious versions

2 flagged

1.6.41.6.6

Indicators of compromise (SHA-256)

1ab82f90e45185d5e25435ce8fc92501dbf7b7384ec6eea6e6b7416ac9426cfb

ce23cdd4a923f1968307c13eec2354aba119dea74d78f7cddf2b7eef442d5148

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for zenntechinc-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 zenntechinc-cli across your stack and pipelines.
If you installed it — respond
zenntechinc-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If zenntechinc-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 zenntechinc-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. zenntechinc-cli on npm has been identified as a malicious package (versions 1.6.4, 1.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018760IN-MAL-2026-018759

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zenntechinc-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database