dolyame-boxy-independent-bnpl-open-apinpm
dolyame-boxy-independent-bnpl-open-api is a confirmed malicious npm package (MAL-2026-12366) that executes malicious code on install (malicious version 20.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-independent-bnpl-open-api (npm)
What this malware does
On require() of the package, index.js loads helpers.js which immediately invokes start(). start() selects a Windows, Linux, or macOS payload path, downloads an opaque native binary via https.get from one of three hardcoded Cloudflare workers.dev hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT-record fallback under *.dl.well1.site, writes it to /tmp/.cache<rand> or %TEMP%/dotnet_diag_<rand>.exe, chmods it 0755, and detached-spawns it via /bin/sh -c or cmd /c start /b. Hostnames are assembled by array-join string concatenation and child_process is loaded via require("child_"+"process") to evade static string scanning. The package advertises itself as a BNPL API SDK; the fetched binary is unrelated to that stated purpose and uses cover-story filenames (dotnet_diag,.cache_). A secondary lib/telemetry.js (~81 KB) bundles structurally identical dropper primitives (https fetch, chmod 0755, /bin/sh -c detached spawn, base64 chunk decode) though it is not reached from the current main.
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 dolyame-boxy-independent-bnpl-open-api (version 20.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-independent-bnpl-open-api across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-independent-bnpl-open-api 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 dolyame-boxy-independent-bnpl-open-api 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 dolyame-boxy-independent-bnpl-open-api 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 dolyame-boxy-independent-bnpl-open-api-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.