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

dolyame-boxy-independent-bnpl-text-blocknpm

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

Malicious code in dolyame-boxy-independent-bnpl-text-block (npm)

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

What this malware does

On require() of the package, index.js loads runtime.js, which assembles Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) and DNS-TXT fallback hosts under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) from split-and-joined string fragments to conceal them from static analysis. It fetches a platform-specific executable payload from those hosts, writes it to a randomly-named file in /tmp or %TEMP% with cover-story names (dotnet_diag<rnd>.exe,.cache_<rnd>,.analytics_state), chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd /c start. The tarball also ships lib/telemetry.js, an ~81KB unreferenced sibling module implementing the same fetch-write-chmod-spawn pattern with base64-reconstructed payload bytes and string-concatenated 'child_'+'process' / 'chmod'+'Sync' references. The package's declared purpose as a BNPL text-block UI helper has no relationship to the observed dropper behavior.

Malicious versions

1 flagged
35.5.3

Indicators of compromise (SHA-256)

0d558b476b362ab912d18912a13c79e326b5fcdcdbe73b0f292d94aa89ac732d

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-text-block (version 35.5.3). 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-text-block across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-boxy-independent-bnpl-text-block 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-text-block 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-text-block 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-text-block on npm has been identified as a malicious package (version 35.5.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015656

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
dolyame-boxy-independent-bnpl-text-block (npm) malicious package — MAL-2026-13332 | O3 Security