xo-twofa
Dependency confusion proof of concept package
This report shows the evidence for xo-twofa@28.0.0. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms unconsented install-time host fingerprint exfiltration. This is concrete malicious behavior, not an inert test artifact.
Decision evidence
public snapshot- package.json runs `node index.js` via preinstall.
- index.js collects hostname, OS, architecture, home directory, and DNS servers.
- index.js POSTs collected host data to f4k2mnpoengdb7o3etftn7fmkdq5ew5ku.oastify.com/hit during install.
- No credential-file reads, shell execution, or payload download found in the inspected files.
- Bundled archive contains the same two-file source.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource collects local host identity data and sends it to an external endpoint.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to xo-twofa@28.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing xo-twofa@28.0.0. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.