@an1mshnpmb9c84920/pipe-dns-m19t2
owned package compatibility control
This report shows the evidence for @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.1. 2 of 5 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe lifecycle hook activates an automatic DNS disclosure of host-identifying data to an unrelated out-of-band recipient. This is concrete install-time collection and transmission, so the package should be blocked.
Decision evidence
public snapshot- package.json runs index.js from an automatic prepare lifecycle script.
- index.js queries DNS with the machine hostname and a derived lookup result encoded under an out-of-band domain, without a consent check.
Source & flagged code
2 flagged · loading sourcepackage.json runs index.js from an automatic prepare lifecycle script.
package.jsonView on unpkg · L1index.js queries DNS with the machine hostname and a derived lookup result encoded under an out-of-band domain, without a consent check.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.