Which versions of verify-cli are malicious?

The following npm versions of verify-cli are flagged malicious: 99.0.0. Treat any of these as compromised.

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

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

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

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

Malicious package

verify-clinpm

verify-cli is a confirmed malicious npm package (MAL-2026-13882) that opens a backdoor for remote access (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in verify-cli (npm)

MAL-2026-13882

Immediate action

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

npm uninstall verify-cli

What this malware does

package.json declares preinstall: node index.js, which runs automatically on npm install. index.js shells out via child_process and curl to POST the installer's whoami, hostname, and id output along with base64-encoded contents of /etc/passwd, /etc/hosts, and (if readable) /etc/shadow to a hardcoded out-of-band interactsh/OAST endpoint at 5f8a1ed70fb7761d678agw9bucryyyyyb.oast.site. Package metadata shows an implausible version (99.0.0), placeholder description ("Nodejs SDK for Redacted"), and a nonexistent dependency, consistent with a dependency-confusion / typosquat beacon rather than a legitimate SDK.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

081d3a8717b3f05f688cdde25d2b0de315dd9b1f400382e0db00d53f8ca82d6b

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

Campaign

IN-MAL-2026-017574

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks verify-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