registry / stillm4ddpocs-demo-sprocket / 999.9.20

stillm4ddpocs-demo-sprocket@999.9.20

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

AI Security Review

scanned 4h ago · by lpm-firewall-ai

npm preinstall runs code that fingerprints the host and consuming project, then sends the data externally. It uses DNS and HTTP(S) channels to increase delivery likelihood.

Static reason

One or more suspicious static signals were detected.

Trigger

npm installation (preinstall); requiring index.js also executes the collection flow.

Impact

Unconsented disclosure of identifying network, user, filesystem-path, host, and project-owner metadata.

Mechanism

install-time host and project metadata exfiltration through DNS and HTTP(S) beacons

Attack narrative

On npm installation, the preinstall hook runs index.js. It reads the consuming project's manifest, gathers host, username, home-directory, working-directory and network-identifying data, performs public-IP and DNS-resolver lookups, then encodes the JSON payload into DNS queries and posts it to a fixed external callback over HTTP and HTTPS. The stated research purpose does not establish consent from affected installers.

Rationale

This is concrete unconsented preinstall-time data exfiltration from the consuming environment through multiple external channels. The absence of credential theft or persistence does not mitigate the malicious install-time beaconing behavior.

Evidence

package.jsonindex.js<INIT_CWD>/package.json

Network endpoints5

da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.funapi.ipify.orgicanhazip.com/ip

stillm4ddpocs-demo-sprocket@999.9.20

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code