Which versions of devplatform-jscodeshift-transforms are malicious?

The following npm versions of devplatform-jscodeshift-transforms are flagged malicious: 35.9.5. Treat any of these as compromised.

How do I remediate devplatform-jscodeshift-transforms if I installed it?

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

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

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

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

Malicious package

devplatform-jscodeshift-transformsnpm

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

Malicious code in devplatform-jscodeshift-transforms (npm)

MAL-2026-12718

Immediate action

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

npm uninstall devplatform-jscodeshift-transforms

What this malware does

On require() of the package, index.js loads shim.js which downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (destinations reconstructed via string-split concatenation such as ["oob-worker.cf102-b","af.workers.","de","v"].join("")), writes it to /var/tmp or %TEMP% under disguised names like dotnet_diag.exe or.cache_, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. When HTTPS retrieval fails, shim.js falls back to a DNS-TXT covert channel: it resolves TXT records on numbered subdomains under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru and base64-reassembles the responses into the executable buffer. API names (require("child" + "process"), fs["chmod" + "Sync"]) are likewise split to evade static analysis, and env-var checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) plus cover-story identifiers (analytics_state, telemetry.js) frame the loader as benign analytics. The package name mimics an internal jscodeshift transforms wrapper.

Malicious versions

1 flagged

35.9.5

Indicators of compromise (SHA-256)

37b642060b8d602b0de19c132a792a4979dafc0cb06590dc2f10d14fe0980151

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

Campaign

IN-MAL-2026-015053

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-jscodeshift-transforms-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