@kibt/www-nuxt-i18nnpm
Advisory published Updated
@kibt/www-nuxt-i18n is a confirmed malicious npm package (MAL-2026-17498) that opens a backdoor for remote access (malicious versions 0.0.1, 0.1.0, 1.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @kibt/www-nuxt-i18n (npm)
What this malware does
The package is a stub whose index.js exports a Proxy returning no-op functions for every property access, allowing bundlers that import any member of the expected real package to succeed. The package.json declares a postinstall script node beacon.cjs, and index.js also loads the same beacon at require() time. beacon.cjs collects installer host metadata — os.hostname(), the install directory (__dirname), process.cwd(), and process.version — and POSTs it to the hardcoded plain-HTTP bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not affiliated with any legitimate publisher, the package provides no real functionality, and an in-source comment frames successful installs as evidence of a hit — matching the canonical dependency-confusion / namesquat validator shape where host identity is reported back to the operator to confirm which internal environments resolved the attacker-controlled scoped name.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for @kibt/www-nuxt-i18n (8 malicious versions).
If you installed it — respond
@kibt/www-nuxt-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 @kibt/www-nuxt-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 @kibt/www-nuxt-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.