MAL-2026-13340 Malicious code in dolyame-boxy-mobile-bnpl-footer (npm)
Malicious package
Published
MAL-2026-13340 is a malicious package: dolyame-boxy-mobile-bnpl-footer (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13340/ (Markdown: https://insights.sbomify.com/MAL-2026-13340/index.md)
- Package
- dolyame-boxy-mobile-bnpl-footer
- Registry
- npm
What is MAL-2026-13340?
MAL-2026-13340 is a malicious package in dolyame-boxy-mobile-bnpl-footer, published on 5 Aug 2026.
Official description
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.
What should I do about MAL-2026-13340?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.