@ecg-internal/js-react-i18nnpm
Advisory published Updated
@ecg-internal/js-react-i18n is a confirmed malicious npm package (MAL-2026-18209) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ecg-internal/js-react-i18n (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @ecg-internal/js-react-i18n (5 malicious versions).
If you installed it — respond
@ecg-internal/js-react-i18n establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @ecg-internal/js-react-i18n was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ecg-internal/js-react-i18n-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.