Which versions of devplatform-spa-plugin-i18next are malicious?

The following npm versions of devplatform-spa-plugin-i18next are flagged malicious: 35.2.1. Treat any of these as compromised.

How do I remediate devplatform-spa-plugin-i18next if I installed it?

Remove devplatform-spa-plugin-i18next from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed devplatform-spa-plugin-i18next — how do I know if it already compromised me?

If devplatform-spa-plugin-i18next 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 devplatform-spa-plugin-i18next part of a known attack campaign?

Yes — devplatform-spa-plugin-i18next is associated with the IN-MAL-2026-015007 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 devplatform-spa-plugin-i18next 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 devplatform-spa-plugin-i18next (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-i18next across your stack and pipelines.

Malicious package

devplatform-spa-plugin-i18nextnpm

devplatform-spa-plugin-i18next is a confirmed malicious npm package (MAL-2026-12768) that executes malicious code on install (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-spa-plugin-i18next (npm)

MAL-2026-12768

Immediate action

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

npm uninstall devplatform-spa-plugin-i18next

What this malware does

index.js unconditionally requires./loader on load. loader.js reassembles Cloudflare workers.dev hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) from split-string arrays, with a DNS-TXT covert-channel fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru (chunk-count from c.<domain>, base64 chunks from numbered subdomains). It fetches a platform-specific native binary, writes it to /var/tmp or %TEMP% under cover names such as dotnet_diag<hex>.exe or.cache<hex>, chmods 0755, and spawns it detached via /bin/sh -c '<file> &' or cmd /c start. A second module lib/telemetry.js (~81KB, disguised as an analytics SDK) duplicates the same fetch+chmod+spawn primitives using string-concatenated identifiers (require("child_"+"process"), fs["chmod"+"Sync"]) as a redundant stage. The i18next plugin name and analytics_state marker do not correspond to any translation functionality shipped in the tarball.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

88e8b3586c4dee4e4e812d6dc1771ec4bc99bc01058c0ae3d2e8c0cdaa8072c8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-spa-plugin-i18next (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-spa-plugin-i18next across your stack and pipelines.
If you installed it — respond
Remove devplatform-spa-plugin-i18next from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If devplatform-spa-plugin-i18next 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 devplatform-spa-plugin-i18next 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. devplatform-spa-plugin-i18next on npm has been identified as a malicious package (version 35.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015007

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-plugin-i18next-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database