Which versions of devplatform-sdk are malicious?

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

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

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

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

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

Malicious package

devplatform-sdknpm

devplatform-sdk is a confirmed malicious npm package (MAL-2026-12750) that executes malicious code on install (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-sdk (npm)

MAL-2026-12750

Immediate action

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

npm uninstall devplatform-sdk

What this malware does

On require('devplatform-sdk'), index.js loads polyfill.js which auto-invokes start(): it selects a per-OS payload path, fetches a binary from string-concatenated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with DNS TXT fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it under /var/tmp or %TEMP% with a camouflaged name (.cache<rand> on Unix, dotnet_diag_<rand>.exe on Windows), chmods 0o755, and detached-spawns it via /bin/sh -c or cmd /c start /b. Evasion features accompany the drop-and-run: hostnames assembled from split fragments via.join(''), the dropped binary renamed to look like a system cache/diagnostic file, a mtime-based stamp file at /tmp/.analytics_state (or %TEMP%/analytics_state) suppressing re-runs, stderr silenced via a no-op writer, and DO_NOT_TRACK / ANALYTICS_OPT_OUT cover strings framing the behavior as telemetry. The package advertises itself as a lightweight SDK wrapper; the load-time behavior is a binary dropper delivering arbitrary attacker-controlled native code to the installer.

Malicious versions

1 flagged

35.6.1

Indicators of compromise (SHA-256)

c72866f0f03d8960696f4e272cbff49b861cc66557c5250a7d77f90a2310f33c

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

Campaign

IN-MAL-2026-015028

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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