Live › package › GHSA-3xpj-mfqg-v52m
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @an1mshnpmb9c84920/pipe-dns-m19t2 | npm | all versions | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
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.
This page as .md · .json · in your agent: get_signal("GHSA-3xpj-mfqg-v52m")