NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @an1mshnpmb9c84920 published 8 malicious packages. See the full campaign →
Malicious package

@an1mshnpmb9c84920/pipeprobe-obf-m19n5npm

Advisory published Updated

@an1mshnpmb9c84920/pipeprobe-obf-m19n5 is a confirmed malicious npm package (MAL-2026-18439) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @an1mshnpmb9c84920/pipeprobe-obf-m19n5 (npm)

MAL-2026-18439
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @an1mshnpmb9c84920/pipeprobe-obf-m19n5

What this malware does

The package's prepare lifecycle script executes node index.js, which reconstructs the hostname npmp19n5--768.oob.awss.dev by joining a string array and issues a DNS lookup via require('dns').lookup(...). The destination is an out-of-band application-security-testing callback host carrying a unique per-package label, so installing the package confirms code execution on the installer's machine to the operator of that domain. The hostname is assembled from an array of fragments at runtime rather than appearing as a plain literal, concealing the destination from static scanners. The package provides no legitimate functionality consistent with a lifecycle-time DNS callback to an external token-bearing host.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

66025f4cca9a4269af1b3b1278d850c9454b62d8e9ec90ad6e4ba8ac73c0fce2

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @an1mshnpmb9c84920/pipeprobe-obf-m19n5 (version 1.0.0).

  2. If you installed it — respond

    Remove @an1mshnpmb9c84920/pipeprobe-obf-m19n5 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @an1mshnpmb9c84920/pipeprobe-obf-m19n5 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. @an1mshnpmb9c84920/pipeprobe-obf-m19n5 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022479

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @an1mshnpmb9c84920/pipeprobe-obf-m19n5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore