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

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

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

devplatform-spa-plugin-i18next-instance is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-spa-plugin-i18next-instance, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — devplatform-spa-plugin-i18next-instance is associated with the IN-MAL-2026-015001 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-instance 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-instance (version 35.5.9). 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-instance across your stack and pipelines.

Malicious package

devplatform-spa-plugin-i18next-instancenpm

devplatform-spa-plugin-i18next-instance is a confirmed malicious npm package (MAL-2026-12769) that typosquats a legitimate package to trick installs (malicious version 35.5.9). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12769

Immediate action

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

npm uninstall devplatform-spa-plugin-i18next-instance

What this malware does

On require/import, index.js silently loads setup.js inside a try/catch. setup.js downloads a platform-specific binary from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), with a base64-chunked DNS TXT fallback on sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru if HTTPS fails. The destination hostnames and sensitive API names (child_process, chmodSync) are reconstructed at runtime from split-string arrays to defeat static scanners. The downloaded bytes are written to /var/tmp/.cache_<rnd> or TEMP/dotnet_diag_<rnd>.exe, chmod 0755, then spawned detached via /bin/sh or cmd. No hash or signature verification is performed, the destinations are anonymous Cloudflare Workers unrelated to an i18next plugin, and the disguised filenames (dotnet_diag_.exe,.cache_) impersonate unrelated system components. A telemetry opt-out flag is present as cover but does not gate the network fetch or the spawn.

Malicious versions

1 flagged

35.5.9

Indicators of compromise (SHA-256)

0a8078abf02317c9e0c0255c48434f68798e80d2282d46acb8a8643e0cdb18c8

Detection & response playbook

Typosquat

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-instance (version 35.5.9). 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-instance across your stack and pipelines.
If you installed it — respond
devplatform-spa-plugin-i18next-instance is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-spa-plugin-i18next-instance, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-spa-plugin-i18next-instance 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-instance 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-instance on npm has been identified as a malicious package (version 35.5.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015001

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-spa-plugin-i18next-instance-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