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

dolyame-boxy-independent-bnpl-code-textnpm

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

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

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

What this malware does

On require() of the package, index.js loads ext.js which fetches a platform-specific executable from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev) with a DNS-TXT covert-channel fallback under *.dl.wel1.ru (c.<domain> for chunk count, i.<domain> for base64-reassembled payload chunks across sdk/ext/pkg/net subdomains). The fetched bytes are written to /tmp or %TEMP% under a disguised name (dotnet_diag<hex>.exe /.cache_<hex>), chmod 755'd, and spawned detached via /bin/sh -c or cmd /c start. Destination hostnames are reconstructed via array-join to evade static string scanning. The behavior is framed as opt-out telemetry (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks,.analytics_state file), and lib/telemetry.js contains a parallel Buffer.from(chunks,'base64') + fs.chmodSync + cp.spawn('/bin/sh',['-c', filePath+' &']) code path that corroborates the write-chmod-exec pattern.

Malicious versions

1 flagged
35.7.8

Indicators of compromise (SHA-256)

bc7222a6cf31e1412fd943bcf3b140b02f6c615b1650f9c39cabf813801557ae

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015676

References

Credits

  • Amazon Inspector · finder

Detect & block this

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