Which versions of @ensdomains/vite-plugin-i18next-loader are malicious?

The following npm versions of @ensdomains/vite-plugin-i18next-loader are flagged malicious: 4.0.4. Treat any of these as compromised.

How do I remediate @ensdomains/vite-plugin-i18next-loader if I installed it?

@ensdomains/vite-plugin-i18next-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @ensdomains/vite-plugin-i18next-loader — how do I know if it already compromised me?

If @ensdomains/vite-plugin-i18next-loader was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @ensdomains/vite-plugin-i18next-loader part of a known attack campaign?

Yes — @ensdomains/vite-plugin-i18next-loader is associated with the GHSA-9g7r-9c2x-w9fj campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ensdomains/vite-plugin-i18next-loader across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ensdomains/vite-plugin-i18next-loader (version 4.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/vite-plugin-i18next-loader across your stack and pipelines.

Malicious package

@ensdomains/vite-plugin-i18next-loadernpm

Malicious code in @ensdomains/vite-plugin-i18next-loader (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190741

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ensdomains/vite-plugin-i18next-loader

What this malware does

The package @ensdomains/vite-plugin-i18next-loader was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

4.0.4

Indicators of compromise (SHA-256)

c80441cca25579f7c8502d6480cda21575480d92e3c38e1f7c734e7f87462f21

473280de7d29dd017bfa50f0826a0aa810d204a6949fe49d6753ff28ff61d505

11a4817b3a5204da9e810eb9085dc5121fd8af83c29c8f73d35d22a6f6096809

498cd9e9ace897a76da2cf0a7cbe5bee289608e99e4c3b0e77d5f95423a5dfd8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ensdomains/vite-plugin-i18next-loader (version 4.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ensdomains/vite-plugin-i18next-loader across your stack and pipelines.
If you installed it — respond
@ensdomains/vite-plugin-i18next-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ensdomains/vite-plugin-i18next-loader was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ensdomains/vite-plugin-i18next-loader before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @ensdomains/vite-plugin-i18next-loader on npm has been identified as a malicious package (version 4.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9g7r-9c2x-w9fj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ensdomains/vite-plugin-i18next-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring