nemo-jaws
Dependency confusion proof of concept package
This report shows the evidence for nemo-jaws@28.0.0. 4 of 4 known versions are blocked or flagged. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource directly confirms unconsented install-time collection and exfiltration of host-identifying data. This is concrete malicious behavior, not a benign package-aligned network action.
Decision evidence
public snapshot- package.json runs `node index.js` in preinstall.
- index.js collects hostname, platform, architecture, home directory, and DNS servers.
- index.js POSTs collected host data to iaw5sqvrkqmghau6kwlwtalpqgw8k88x.oastify.com/hit.
- The nested tarball contains the same lifecycle script and collector.
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 nemo-jaws@28.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nemo-jaws@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.