Which versions of devplatform-i18n are malicious?

The following npm versions of devplatform-i18n are flagged malicious: 35.6.2. Treat any of these as compromised.

How do I remediate devplatform-i18n if I installed it?

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

I already installed devplatform-i18n — how do I know if it already compromised me?

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

Yes — devplatform-i18n is associated with the IN-MAL-2026-015054, GHSA-955v-2fx5-8jjw 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-i18n 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-i18n (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-i18n across your stack and pipelines.

Malicious package

devplatform-i18nnpm

devplatform-i18n is a confirmed malicious npm package (MAL-2026-12714) that typosquats a legitimate package to trick installs (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-i18n (npm)

MAL-2026-12714

Immediate action

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

npm uninstall devplatform-i18n

What this malware does

Package is published as an i18n library but its main entry (index.js) requires./setup on load. setup.js selects a per-platform payload path, fetches bytes over HTTPS from mirror hosts assembled at runtime via array-join (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT chunked base64 fallback via subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c '<path> &' or cmd /c start. A stamp file rate-limits re-execution. A parallel loader in lib/telemetry.js reconstructs a base64 payload from DNS TXT chunks and executes it through the same write+chmod+spawn chain; dangerous API references are hidden via string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]). Destination hosts, module names, and filesystem APIs are all obfuscated via array-join and string concatenation, and the dropped filenames mimic OS cache/diagnostic files.

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

1 flagged

35.6.2

Indicators of compromise (SHA-256)

30b21acc89730541bc58390e2694a9e5410417e5232bb4f4d47c0c27b035e2f4

2a340322be600687a0c7f8d2a109863bf8544e0a8637184db038b9ff8861810e

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-i18n (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-i18n across your stack and pipelines.
If you installed it — respond
devplatform-i18n is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-i18n, 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-i18n 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-i18n 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-i18n on npm has been identified as a malicious package (version 35.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015054GHSA-955v-2fx5-8jjw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-i18n-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