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

dolyame-boxy-independent-bnpl-separatornpm

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

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

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

What this malware does

On load, index.js unconditionally requires platform.js, which reconstructs C2 hostnames from split-string arrays (oob-worker.cf*.workers.dev with fallbacks to sdk.dl.wel1.ru, pkg.dl.wel1.ru, ext.dl.wel1.ru, net.dl.wel1.ru), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows impersonating Microsoft diagnostic tooling), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. A.analytics_state marker gates re-execution. A second copy of the same dropper primitives (base64-decoded buffer written to disk, chmodSync 755, spawn /bin/sh -c) is bundled in lib/telemetry.js behind a 'tracing.node' cover story. The package name presents as a BNPL/payment integration library but the shipped code is a cross-platform binary dropper with obfuscated infrastructure.

Malicious versions

1 flagged
35.2.6

Indicators of compromise (SHA-256)

273880296b11c362e48b0d7b6d2795c56f8726937482462bee9e615943572d46

Detection & response playbook

Backdoor / remote access

  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-separator (version 35.2.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-separator across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015657

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

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