NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-boxy-independent-bnpl-tilesnpm

Advisory published Updated

dolyame-boxy-independent-bnpl-tiles is a confirmed malicious npm package (MAL-2026-13333) that executes malicious code on install (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-independent-bnpl-tiles (npm)

MAL-2026-13333
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-boxy-independent-bnpl-tiles

What this malware does

On require of the package, index.js loads setup.js, which reconstructs attacker-controlled hostnames by splitting string literals across arrays and joining them (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev), fetches an opaque platform-specific binary over HTTPS from those hosts, writes it to a disguised temp path (names like.cache_* and dotnet_diag_*.exe), sets the executable bit via fs.chmodSync(outPath, 0o755), and spawns it detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) (with a cmd branch for Windows). A base64-over-DNS-TXT fallback channel is implemented against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, reading a chunk count from c.<domain> and reassembling base64 TXT chunks into the payload. No native source is shipped that would justify a binary download, and the destinations are unrelated to any declared publisher. A second module lib/telemetry.js is not reached from main in this version but contains the same fetch/chmod/spawn dropper pattern.

Malicious versions

1 flagged
35.7.4

Indicators of compromise (SHA-256)

4340fab762980b85544094ef1795fd82968bb58c7fe0f17a00f50b2df89b29d5

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for dolyame-boxy-independent-bnpl-tiles (version 35.7.4).

  2. If you installed it — respond

    Remove dolyame-boxy-independent-bnpl-tiles 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.

  3. Did it already run?

    If dolyame-boxy-independent-bnpl-tiles was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-boxy-independent-bnpl-tiles on npm has been identified as a malicious package (version 35.7.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015659

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-independent-bnpl-tiles-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.

Explore

dolyame-boxy-independent-bnpl-tiles (npm) malicious package — MAL-2026-13333 | O3 Security