@ecg-internal/js-react-i18n@1.1.0
OpenSSF/OSV Malicious Advisory
imported 2h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18209 confirms this npm version as malicious.
Advisory
MAL-2026-18209
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @ecg-internal/js-react-i18n (npm)
Details
The package is published under an internal-looking scope (@ecg-internal) and ships a stub main module that returns a Proxy of no-op functions for every property access — it provides none of the i18n functionality its name implies. Its only real behavior is firing beacon.cjs, which executes both from the declared postinstall lifecycle script (`node beacon.cjs`) and from a top-level `require('./beacon.cjs').fire()` in the main module. beacon.cjs collects the installer's hostname (via `os.hostname()`), install path (`__dirname`), current working directory, Node.js version, and package name, and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not a publisher-aligned domain and the shape — internal-looking scope + hollow functional surface + install- and import-time callback with host identifiers to a bare IP — is a dependency-confusion reconnaissance probe designed to identify internal build systems that resolve the private name from the public registry.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @ecg-internal/js-react-i18n@1.1.0.
The same advisory and Firewall decision cover 4 recorded versions
1.0.0, 1.0.1, 1.1.0, 2.0.0
See all versions of @ecg-internal/js-react-i18n for other recorded verdicts.
- Avoid installing @ecg-internal/js-react-i18n@1.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: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.