NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@assetshop/verify-clinpm

Advisory published Updated

@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
  1. Find it

    Search your lockfiles and build artifacts for @assetshop/verify-cli (2 malicious versions).

  2. 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.

  3. Did it already run?

    If @assetshop/verify-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Explore

@assetshop/verify-cli (npm) malicious package — MAL-2026-13881 | O3 Security