Which versions of @assetshop/verify-cli are malicious?

The following npm versions of @assetshop/verify-cli are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate @assetshop/verify-cli if I installed it?

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

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

Yes — @assetshop/verify-cli is associated with the IN-MAL-2026-017573, IN-MAL-2026-017572 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 @assetshop/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 @assetshop/verify-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 @assetshop/verify-cli across your stack and pipelines.

Malicious package

@assetshop/verify-clinpm

@assetshop/verify-cli is a confirmed malicious npm package (MAL-2026-13881) that opens a backdoor for remote access (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @assetshop/verify-cli (npm)

MAL-2026-13881

Immediate action

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

npm uninstall @assetshop/verify-cli

What this malware does

On npm install, the package's preinstall hook executes index.js, which collects installer identity and host information — whoami (via execSync), os.hostname(), os.platform(), os.arch(), process.cwd(), os.homedir(), and Node version — and transmits them to a hardcoded Interactsh/OAST callback subdomain at 5f8a1ed70fb7761d678agw9bapayyyyyb.oast.site via an HTTPS GET (with the collected values placed in the URL path) and a DNS lookup of ${user}.${hostname}.assetshop-verify-cli.<oast-host>. The package name in the @assetshop scope combined with the OAST beacon shape is the standard dependency-confusion reconnaissance pattern used to prove internal-name resolution against a private registry.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

7cace01fe47bda782a3a3af79a03154284b0e58f811cf19a63942a02aa5f7342

85394a6ca736d2983eb7f6be36a813afc346a5b3d7edd638cbbda453274630f0

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 @assetshop/verify-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 @assetshop/verify-cli across your stack and pipelines.
If you installed it — respond
@assetshop/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 @assetshop/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 @assetshop/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. @assetshop/verify-cli on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017573IN-MAL-2026-017572

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @assetshop/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