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

dolyame-boxy-independent-bnpl-breadcrumbsnpm

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

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

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

What this malware does

index.js unconditionally requires./_init at module load time. _init.js selects a platform-specific path, fetches an opaque native binary over HTTPS from a rotating set of Cloudflare Workers subdomains whose hostnames are assembled at runtime via array.join("") to evade plain-text scanning (e.g. oob-worker.cf99-9b3.workers.dev, cf101-adf/cf103-070/cf100-416.workers.dev), writes it to /tmp or %TEMP% under a disguised name, chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A fallback covert channel queries TXT records at c.<domain> and N.<domain> under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, concatenates the chunks and base64-decodes them into the same executable payload. Requiring or installing the package results in execution of attacker-controlled native code on the installer host.

Malicious versions

1 flagged
35.1.4

Indicators of compromise (SHA-256)

95d52abe2ced4314ede2df4d3475d73fb87f52298434cdbf6469bf057613346f

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-breadcrumbs (version 35.1.4). 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-breadcrumbs across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015685

References

Credits

  • Amazon Inspector · finder

Detect & block this

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