@an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe 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.
Decision evidence
public snapshot- 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.
- 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.
Source & flagged code
2 flagged · loading sourceThe manifest embeds shell command substitution containing a DNS lookup in its repository URL; it has no lifecycle scripts.
package.jsonView on unpkg · L1The entrypoint only exports the number 1 and contains no visible execution logic.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5.
See all versions of @an1mshnpmb9c84920/pipe-dns-m19t2 for other recorded verdicts.
- Review the evidence and your use of @an1mshnpmb9c84920/pipe-dns-m19t2@1.0.5 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.