What does the devplatform-jscodeshift-plugin malware do?

On require(), index.js loads _loader.js, which reconstructs Cloudflare Workers hostnames from split string fragments (e.g. ['oob-worke','r.cf101-a','df.workers.d','ev'].join('')) and a DNS-TXT fallback channel via fragmented 'sdk.dl.wel1.ru' resolvers, downloads a platform-specific binary, writes it to /var/tmp/.cache_ on Unix or %TEMP%\dotnet_diag_ .exe on Windows, chmods it 0o755, and spawns it detached via cp.spawn('/bin/sh',['-c', fp+' &']) or spawn('cmd',...). The dropped artifacts use names impersonating telemetry / dotnet diagnostics, and environment variables like DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK are honored to provide a cover story. The package has no jscode

Which versions of devplatform-jscodeshift-plugin are malicious?

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

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

devplatform-jscodeshift-plugin 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 devplatform-jscodeshift-plugin — how do I know if it already compromised me?

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

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

Malicious package

devplatform-jscodeshift-pluginnpm

devplatform-jscodeshift-plugin is a confirmed malicious npm package (MAL-2026-12717) that steals credentials and exfiltrates sensitive data (malicious version 35.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-jscodeshift-plugin (npm)

MAL-2026-12717

Immediate action

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

npm uninstall devplatform-jscodeshift-plugin

What this malware does

On require(), index.js loads loader.js, which reconstructs Cloudflare Workers hostnames from split string fragments (e.g. ['oob-worke','r.cf101-a','df.workers.d','ev'].join('')) and a DNS-TXT fallback channel via fragmented 'sdk.dl.wel1.ru' resolvers, downloads a platform-specific binary, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods it 0o755, and spawns it detached via cp.spawn('/bin/sh',['-c', fp+' &']) or spawn('cmd',...). The dropped artifacts use names impersonating telemetry / dotnet diagnostics, and environment variables like DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK are honored to provide a cover story. The package has no jscodeshift-plugin functionality and appears to be a name-squat lure whose only purpose is dropping and executing this remote payload.

Malicious versions

1 flagged

35.4.1

Indicators of compromise (SHA-256)

92dcd946aaaf9b57795f9a94877df34a69ac39828620c58e2cf4b72cd7a9c253

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

Campaign

IN-MAL-2026-015055

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database