NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-boxy-atom-bnpl-buttonnpm

Advisory published Updated

dolyame-boxy-atom-bnpl-button is a confirmed malicious npm package (MAL-2026-13283) that opens a backdoor for remote access (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-atom-bnpl-button (npm)

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

What this malware does

On require, index.js loads helpers.js which fetches a platform-specific binary from obfuscated hosts assembled via array-join (oob-worker.cf*.workers.dev) with a DNS-TXT chunked-base64 fallback channel to *.dl.wel1.ru, writes the bytes to /tmp/.cache<rnd> or %TEMP%/dotnet_diag_<rnd>.exe, chmods 0755, and spawns the file detached via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}) or cmd equivalent on Windows. No integrity or signature check is performed on the fetched bytes. Destination hostnames are string-split to evade static detection, and file/lock names (analytics_state, dotnet_diag_.exe,.cache_) plus code comments framing the spawn as 'Detached process to avoid blocking npm install' present the behavior as telemetry. A lockfile with a ~22000s max age throttles re-fetching into a scheduled beacon pattern. The DNS-TXT channel provides a covert payload path when HTTPS egress is blocked. Any installer requiring this package executes attacker-controlled arbitrary code on their host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
35.8.3

Indicators of compromise (SHA-256)

963f070cd6563a11008f0726b4e0a11e5612dce9b53c58d9ea537566ab1774e2
4fcffe6de0ccd3c2c780baeec4bc4617727847bcd6170d0bd92d067abc3fade4

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for dolyame-boxy-atom-bnpl-button (version 35.8.3).

  2. If you installed it — respond

    dolyame-boxy-atom-bnpl-button establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If dolyame-boxy-atom-bnpl-button was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015720GHSA-xp3x-7m7p-57w6

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-atom-bnpl-button-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

dolyame-boxy-atom-bnpl-button (npm) malicious package — MAL-2026-13283 | O3 Security