Which versions of devplatform-api-v2-endpoint are malicious?

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

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

devplatform-api-v2-endpoint establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed devplatform-api-v2-endpoint — how do I know if it already compromised me?

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

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

Malicious package

devplatform-api-v2-endpointnpm

devplatform-api-v2-endpoint is a confirmed malicious npm package (MAL-2026-12694) that opens a backdoor for remote access (malicious version 35.6.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-api-v2-endpoint (npm)

MAL-2026-12694

Immediate action

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

npm uninstall devplatform-api-v2-endpoint

What this malware does

On require(), index.js loads./vendor, whose top-level init() fetches a platform-specific native binary from runtime-assembled Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a fallback that reassembles a base64-encoded binary from DNS TXT records under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The retrieved bytes are written to /var/tmp or %TEMP% under cover-story names such as.cache<rand> and dotnet_diag_<rand>.exe, chmod 0755, and detached-spawned via /bin/sh -c or cmd.exe /c start /b. C2 hostnames are constructed by joining split string fragments to evade static scanners, and the package labels the activity as 'analytics'/'telemetry'. The result is arbitrary attacker-controlled code execution on the installer's host on every import of the package.

Malicious versions

1 flagged

35.6.7

Indicators of compromise (SHA-256)

6f78874e3ff64b85f64b75f0481a7cadc00f15dea7b4f0eb85c1728a65ee2020

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-api-v2-endpoint (version 35.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-api-v2-endpoint across your stack and pipelines.
If you installed it — respond
devplatform-api-v2-endpoint establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If devplatform-api-v2-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-v2-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-v2-endpoint on npm has been identified as a malicious package (version 35.6.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015081

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-api-v2-endpoint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database