bnpl-forms-test-utilsnpm
bnpl-forms-test-utils is a confirmed malicious npm package (MAL-2026-13024) that executes malicious code on install (malicious version 35.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-forms-test-utils (npm)
What this malware does
On require('bnpl-forms-test-utils'), index.js loads platform.js, which selects a platform-specific endpoint and downloads an opaque binary via https.get from one of three Cloudflare Workers hosts reconstructed at runtime from split-string arrays: oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, and oob-worker.cf103-070.workers.dev. A DNS TXT fallback under {sdk,ext,pkg,net}.dl.wel1.ru reassembles base64 chunks when the HTTPS hosts fail. The fetched bytes are written to /var/tmp or %TEMP% under masquerading names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and detached via spawn('/bin/sh', ['-c', path+' &'], {detached:true}) or spawn('cmd.exe', ['/c', 'start',...]). Hostnames and API names are obfuscated via array-join and string concatenation (e.g. require('child_'+'process'), fs['chmod'+'Sync']). A second dropper module lib/telemetry.js (~81 KB) shipped in the tarball implements the same fetch/chmod/spawn/detach pattern with identical obfuscation, though it is not referenced from the current main. The declared purpose is common helpers; no native source ships in the package to justify the binary download.
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 bnpl-forms-test-utils (version 35.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-forms-test-utils across your stack and pipelines.
If you installed it — respond
Remove bnpl-forms-test-utils 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 bnpl-forms-test-utils 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 bnpl-forms-test-utils 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 bnpl-forms-test-utils-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.