devplatform-integrations-tests-libnpm
devplatform-integrations-tests-lib is a confirmed malicious npm package (MAL-2026-12716) that typosquats a legitimate package to trick installs (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in devplatform-integrations-tests-lib (npm)
What this malware does
On require, bootstrap.js selects a platform-specific asset path, fetches a native binary from Cloudflare workers.dev hosts (e.g. oob-worker.cf101-adf.workers.dev) with a DNS-TXT fallback to *.dl.wel1.ru, writes it to /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames and DNS domains are assembled from split string arrays (e.g. ['sdk.d','l.wel','1.ru'].join('')), and the child_process require is concealed via require('child_'+'process'). Staging filenames (analytics_state, dotnet_diag_*.exe) mimic legitimate system artifacts. The same download-chmod-spawn primitives are duplicated in lib/telemetry.js, providing a secondary load-time execution path. The package name and 'telemetry' framing are a cover for the dropper behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for devplatform-integrations-tests-lib (version 35.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging devplatform-integrations-tests-lib across your stack and pipelines.
If you installed it — respond
devplatform-integrations-tests-lib is a typosquat — you almost certainly intended a legitimately-named package. Remove devplatform-integrations-tests-lib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If devplatform-integrations-tests-lib 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-integrations-tests-lib 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-integrations-tests-lib-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.