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

dolyame-boxy-desktop-bnpl-image-plus-textnpm

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

Malicious code in dolyame-boxy-desktop-bnpl-image-plus-text (npm)

MAL-2026-13306
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-boxy-desktop-bnpl-image-plus-text

What this malware does

On require() of this package, index.js loads compat.js which selects platform-specific endpoints assembled from split string arrays (e.g. oob-worker.cf10-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) and downloads an opaque binary via https.get. If HTTP fetch fails, a fallback path reassembles a base64 payload from numbered DNS TXT records under *.dl.wel1.ru — a covert channel designed to bypass HTTP egress controls. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name (.cache_XXXX on POSIX, dotnet_diag_XXXX.exe on Windows), chmod'd 0755, and spawned detached via /bin/sh -c or cmd.exe. A second module lib/telemetry.js (81KB) bundled in the tarball mirrors the same fetch/chmod/spawn chain using string-concatenation obfuscation of 'child' + 'process' and 'chmod' + 'Sync', framed as an Analytics SDK; it is not reached from index.js in this version but is a one-line change from activation. The package name presents as a Dolyame BNPL desktop UI component, unrelated to the observed dropper behavior. No hash verification, no publisher pinning, and hostname obfuscation together characterize this as a lure package delivering attacker-controlled code to the installer's host at require() time.

Malicious versions

1 flagged
35.3.2

Indicators of compromise (SHA-256)

4501ea4e0c044573a1d76bf04ee806de26c33bd1dc38f21a2d1f00988a96e656

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-desktop-bnpl-image-plus-text (version 35.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-desktop-bnpl-image-plus-text across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015687

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-desktop-bnpl-image-plus-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