Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@an1mshnpmb9c84920/pipe-dns-m19t2npm

Advisory published Updated

@an1mshnpmb9c84920/pipe-dns-m19t2 is a confirmed malicious npm package (MAL-2026-18049) 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/pipe-dns-m19t2 (npm)

MAL-2026-18049
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @an1mshnpmb9c84920/pipe-dns-m19t2

What this malware does

The package's prepare lifecycle script executes index.js, which builds a subdomain string from the installer's hostname and the npm lifecycle event name and issues a dns.lookup against npmexec19t2--768.oob.awss.dev, an authoritative zone controlled by the publisher. This leaks installer identity to an external party automatically on npm install via an out-of-band DNS channel. The package.json repository field points at a sibling host on the same oob.awss.dev infrastructure, and the README contains only the word 'owned', with no legitimate functionality shipped in the tarball.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

0af2574cde6941a12e82bbc6fb4de1d1fd75b2434ab5e88dbebc4e8ea644bd36
548a4b4d6c63df4cc62bd7e753758dc32f98b3ed9adb7fbee204493838614eea

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @an1mshnpmb9c84920/pipe-dns-m19t2 (version 1.0.0).

  2. If you installed it — respond

    Remove @an1mshnpmb9c84920/pipe-dns-m19t2 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/pipe-dns-m19t2 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/pipe-dns-m19t2 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

GHSA-3xpj-mfqg-v52mIN-MAL-2026-021528

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @an1mshnpmb9c84920/pipe-dns-m19t2-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

@an1mshnpmb9c84920/pipe-dns-m19t2 (npm) malicious package — MAL-2026-18049 | O3 Security