Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dolyame-boxy-independent-bnpl-searchnpm

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

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

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

What this malware does

On require, index.js loads init.js which reconstructs hostnames from split-string arrays (e.g. ['oob-worker.cf102','-baf.workers.','dev'].join('') and ['sdk.dl.','wel1.ru'].join('')) to build URLs against four Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. A platform-specific binary is downloaded via https.get, written to /tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, chmodded 0755, and launched detached via spawn('/bin/sh', ['-c', path+' &']) or spawn('cmd',...). The fetched payload is unverified, comes from mutable non-publisher hosts, and executes on module load rather than through any documented API of the package.

Malicious versions

1 flagged
35.5.6

Indicators of compromise (SHA-256)

4f29e1e3b6b3a01a935dbcd19077e516c17d31c3674078ecfe2cd112b0137437

Detection & response playbook

Malicious package
  1. Find 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-search (version 35.5.6). 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-search across your stack and pipelines.

  2. If you installed it — respond

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

  4. How O3 protects you

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

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

Campaign

IN-MAL-2026-015668

References

Credits

  • Amazon Inspector · finder

Detect & block this

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