devplatform-sre-devplatform-sre-corenpm
devplatform-sre-devplatform-sre-core is a confirmed malicious npm package (MAL-2026-13264) that executes malicious code on install (malicious version 35.1.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-sre-devplatform-sre-core (npm)
What this malware does
On require() of this package, index.js loads helpers.js which selects an OS/arch-specific path and downloads a native binary from one of three Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) whose hostnames are reconstructed at runtime via array.join("") to evade static analysis. The binary is written to /tmp or the Windows Temp directory under disguised names (dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755'd, and spawn-detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. A DNS-TXT covert-channel fallback under *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) reassembles the payload from base64-encoded TXT records (count record c.<domain>, chunk records i.<domain>) when HTTPS delivery fails, then writes and executes the same way. A lockfile named.analytics_state and dotnet_diag-style filenames provide the cover story. This grants full remote code execution to whoever controls those endpoints on any machine that installs or imports the package.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-sre-devplatform-sre-core (version 35.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-sre-devplatform-sre-core across your stack and pipelines.
If you installed it — respond
Remove devplatform-sre-devplatform-sre-core 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-sre-devplatform-sre-core 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-sre-devplatform-sre-core 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks devplatform-sre-devplatform-sre-core-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.