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

dolyame-boxy-independent-bnpl-main-titlenpm

dolyame-boxy-independent-bnpl-main-title is a confirmed malicious npm package (MAL-2026-13552) that steals credentials and exfiltrates sensitive data (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-independent-bnpl-main-title (npm)

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

What this malware does

On require, index.js loads polyfill.js which reconstructs hostnames from split string fragments (e.g., 'oob-worker.cf99-9b3.wor'+'ke'+'rs.dev') to reach multiple Cloudflare Workers subdomains, downloads an opaque platform-specific binary, writes it to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd with stdio ignored. A DNS TXT chunked-transfer fallback under *.dl.wel1.ru reassembles a base64 payload when HTTPS is blocked. Cover-story naming — file polyfill.js, cache marker analytics_state, Windows payload dotnet_diag<hex>.exe, and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT env vars — disguises the fetch-and-exec chain in a package that advertises itself as a BNPL module.

Malicious versions

1 flagged
35.5.6

Indicators of compromise (SHA-256)

7fd169fe81bc68427ce8c3b472cb376e6d3fdad489d07595a8c8f08f894ac154

Detection & response playbook

Credential / info stealer

  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-main-title (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-main-title across your stack and pipelines.

  2. If you installed it — respond

    dolyame-boxy-independent-bnpl-main-title is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If dolyame-boxy-independent-bnpl-main-title 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-main-title 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-main-title 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-017042

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-independent-bnpl-main-title-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
dolyame-boxy-independent-bnpl-main-title (npm) malicious package — MAL-2026-13552 | O3 Security