dolyame-boxy-mobile-bnpl-footernpm
dolyame-boxy-mobile-bnpl-footer is a confirmed malicious npm package (MAL-2026-13340) that executes malicious code on install (malicious version 35.4.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-mobile-bnpl-footer (npm)
What this malware does
The package's main entry (index.js) requires./compat, which at import time downloads a platform-specific executable from author-controlled endpoints assembled at runtime by joining string arrays: oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, and oob-worker.cf103-070.workers.dev. A fallback path reconstructs a base64 payload from DNS TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. A per-platform download map selects /pkg/package (linux_x64), /pkg/loader_mac (darwin), or /pkg/package.exe (win32). The fetched bytes are written to a decoy path (/tmp/.cache<hex> on Unix or TEMP/dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and spawned detached via /bin/sh -c '<file> &' or cmd.exe start /b. lib/telemetry.js ships a second copy of the same primitive under an SDK/telemetry cover story: child_process is acquired via require("child_"+"process"), fs.chmodSync is called as fs["chmod"+"Sync"], and the payload is reassembled with Buffer.from(chunks,"base64") before being spawned. Hostnames, function names, and dropped-file names are constructed at call time to evade static inspection, and the persisted file uses hidden dotfile / Windows diagnostic-tool decoy names (.cache_<hex>, dotnet_diag_<hex>.exe,.analytics_state). The package name presents as a payment/BNPL footer component, which does not match the observed behavior.
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-mobile-bnpl-footer (version 35.4.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-mobile-bnpl-footer across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-mobile-bnpl-footer 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-mobile-bnpl-footer 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-mobile-bnpl-footer 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-mobile-bnpl-footer-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.