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

dolyame-boxy-independent-bnpl-swaggernpm

Advisory published Updated

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

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

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

What this malware does

dolyame-boxy-independent-bnpl-swagger ships an index.js that unconditionally requires setup.js on load. setup.js reconstructs remote hostnames from array-fragment string joins (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) to defeat literal-string scanning, downloads a per-platform binary payload, writes it to /tmp as a hidden dotfile on Unix or to the Windows temp directory as dotnet_diag_*.exe, sets mode 0755, and spawns it detached via /bin/sh -c or cmd.exe. When HTTPS delivery fails, it falls back to a DNS TXT covert channel against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru: it reads a record count from c.<domain> and reassembles base64-encoded binary bytes from numbered TXT records. The fetched code is unpinned, unsigned, and unrelated to the package's declared BNPL swagger purpose. A separate lib/telemetry.js bundles the same drop-and-exec primitives (fs["chmod"+"Sync"], cp.spawn("/bin/sh", ["-c", filePath+" &"])) using bracket-string reconstruction; it is not reachable from the current main entrypoint but is staged in the tarball.

Malicious versions

1 flagged
35.6.8

Indicators of compromise (SHA-256)

8c9922ed471321378d155bfabb5d15f3efe59f8524e30face28e25dadd3305b3

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for dolyame-boxy-independent-bnpl-swagger (version 35.6.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015662

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-independent-bnpl-swagger-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-swagger (npm) malicious package — MAL-2026-13330 | O3 Security