Which versions of devplatform-api-endpoint are malicious?

The following npm versions of devplatform-api-endpoint are flagged malicious: 35.2.9. Treat any of these as compromised.

How do I remediate devplatform-api-endpoint if I installed it?

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

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

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

Malicious package

devplatform-api-endpointnpm

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

Malicious code in devplatform-api-endpoint (npm)

MAL-2026-12692

Immediate action

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

npm uninstall devplatform-api-endpoint

What this malware does

On require() of the package's main entry, index.js unconditionally loads bootstrap.js, which fetches a platform-specific binary from Cloudflare Workers hosts whose names are constructed by concatenating fragmented string literals (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev). The downloaded bytes are written to a temp path with a masquerading filename (dotnet_diag.exe,.cache_), chmod 0755'd, and spawned detached via child_process (/bin/sh -c or cmd.exe /c start). A DNS-TXT covert-channel fallback resolves TXT records under *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) enumerated as c.<domain>, 0.<domain>, 1.<domain>,... and base64-decodes the concatenated TXT payloads into an executable that is then written and run. Endpoint literals are fragmented (e.g., ["oob-worker.cf101-","ad","f.workers.d","ev"].join("")) purely to evade static matching. The package advertises no purpose that justifies fetching and executing remote binaries.

Malicious versions

1 flagged

35.2.9

Indicators of compromise (SHA-256)

4a79a64efe72b14455f83f667581664c2369f92f669983a58cede299f70bcadc

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

Campaign

IN-MAL-2026-015082

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-api-endpoint-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