stillm4ddpocs-demo-widget
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-widget@999.9.9, the only known version.
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-aiSource confirms automatic preinstall execution and external transmission of identifying host and project data. The stated research purpose does not remove the concrete unconsented exfiltration behavior.
Decision evidence
public snapshot- `preinstall` executes `index.js` automatically.
- Install code reads consumer-project metadata and host identity.
- Collected data is encoded into DNS queries and POSTed to an external callback.
- The package is explicitly positioned as a dependency-confusion proof of concept.
- No credential, environment-variable, or arbitrary file-content harvesting is present.
- No persistence, payload download, shell execution, or destructive action is present.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to stillm4ddpocs-demo-widget@999.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing stillm4ddpocs-demo-widget@999.9.9. 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.