Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@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)

MAL-2026-17498
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @kibt/www-nuxt-i18n

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

8 flagged
0.0.10.1.01.0.01.0.11.1.02.0.13.0.099.0.1

Indicators of compromise (SHA-256)

485839cc6750a2751283c1a9453c7b28bf58a29ca316cdb5c4e3027afc2e731b
ec95d08e30fac283e7a552bcf9bd48a3d3059a6c92ea5f6b846ed1bd3dccc402
f85cda0eb18d988d0bc6c5f066f764e86756851f34449942c7ca858a46b22577
5ab1895c73507311b9efd31e40015529d9d7735c87e50cf3b714e6e520205ec4
98b7faf73b0fb9d003258f882b09b23728db415cdf504436021d32f6ac791a29
c3dd2ab4972bdf73b521c63a38dd410378d0ad84f6485ededddd423e19e4ac7f
cf82f32b9ae316d7d4931838da5479339785b611adc42d220bd65feca5bdd8ee
d89b7fb5a53b101194ba86edae564e7cbd573f51001004f536e8b1e6a2d98962
c6086a597c82083008b56986eb1c97cc226ee28f095e500ecd0fc9259536c783

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @kibt/www-nuxt-i18n (8 malicious versions).

  2. 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.

  3. 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

No. @kibt/www-nuxt-i18n on npm has been identified as a malicious package (versions 0.0.1, 0.1.0, 1.0.0, 1.0.1, 1.1.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020917IN-MAL-2026-020915IN-MAL-2026-020911IN-MAL-2026-020912IN-MAL-2026-020913IN-MAL-2026-020914IN-MAL-2026-020919IN-MAL-2026-020916GHSA-2c7v-rmgw-3xrp

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.

Explore