stillm4ddpocs-demo-sprocket
AUTHORISED SECURITY RESEARCH — dependency confusion proof of concept. This package was published because the name appeared in publicly served code but was unregistered on the public registry. If it is in your dependency tree, your resolver fetched an inte
This report shows the evidence for stillm4ddpocs-demo-sprocket@999.9.12. 3 of 3 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 2mo ago · by lpm-firewall-aiDirect source inspection confirms a reachable preinstall reconnaissance and data-exfiltration chain. This is concrete unconsented install-time behavior, independent of the package's stated research intent.
Decision evidence
public snapshot- preinstall automatically executes index.js during npm installation.
- Source reads consuming project's manifest and host/user/home/network identifiers.
- It queries public-IP services and a DNS resolver to expand collected network data.
- It hex-encodes the collected JSON into DNS requests and also POSTs it to an external callback.
- No code writes files, downloads payloads, or invokes shell commands.
- README describes the behavior as security research, but source confirms unconsented install-time collection and transmission.
Source & flagged code
6 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpreinstall automatically executes index.js during npm installation.
package.jsonView on unpkg · L10Findings
Affected versions and remediation
This report applies to stillm4ddpocs-demo-sprocket@999.9.12.
The versions list below shows the verdict for each recorded version.
- Avoid installing stillm4ddpocs-demo-sprocket@999.9.12. 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.