dolyame-boxy-atom-bnpl-email-formnpm
dolyame-boxy-atom-bnpl-email-form is a confirmed malicious npm package (MAL-2026-12363) that executes malicious code on install (malicious version 20.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-atom-bnpl-email-form (npm)
What this malware does
On require of the package's main, index.js side-loads _runtime.js which selects a per-platform payload path, fetches an opaque binary from string-split obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to /var/tmp or %TEMP% with a disguised filename (.cache_<hex>, dotnet_diag_<hex>.exe, .analytics_state), chmods 0755, and spawns it detached via child_process.spawn('/bin/sh') or spawn('cmd'). When the HTTPS mirrors fail, _runtime.js falls back to a DNS TXT covert channel: it resolves c.<domain> for a chunk count, iterates <i>.dl.well1.site TXT records (tin/tina/ldr/win subdomains), concatenates and base64-decodes them into the payload, then writes and spawns it. Host names, fallback DNS domains, and the string 'child_process' are assembled from split string arrays at runtime to evade static analysis. There is no version pinning, hash check, or signature verification, and the destinations are not the publisher's infrastructure. Cover-story framing as an 'Analytics SDK' with a DISABLE_TELEMETRY opt-out does not match the actual fetch-decode-write-chmod-spawn behavior.
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-atom-bnpl-email-form (version 20.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-atom-bnpl-email-form across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-atom-bnpl-email-form 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-atom-bnpl-email-form 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-atom-bnpl-email-form 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-atom-bnpl-email-form-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.