Which versions of dolyame-boxy-independent-bnpl-documents are malicious?

The following npm versions of dolyame-boxy-independent-bnpl-documents are flagged malicious: 35.1.7. Treat any of these as compromised.

How do I remediate dolyame-boxy-independent-bnpl-documents if I installed it?

dolyame-boxy-independent-bnpl-documents is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-independent-bnpl-documents, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed dolyame-boxy-independent-bnpl-documents — how do I know if it already compromised me?

If dolyame-boxy-independent-bnpl-documents 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.

Is dolyame-boxy-independent-bnpl-documents part of a known attack campaign?

Yes — dolyame-boxy-independent-bnpl-documents is associated with the IN-MAL-2026-015670 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-boxy-independent-bnpl-documents across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-independent-bnpl-documents (version 35.1.7). 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-documents across your stack and pipelines.

Malicious package

dolyame-boxy-independent-bnpl-documentsnpm

dolyame-boxy-independent-bnpl-documents is a confirmed malicious npm package (MAL-2026-13316) that typosquats a legitimate package to trick installs (malicious version 35.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-13316

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-boxy-independent-bnpl-documents

What this malware does

On require() of the package's main index.js, bridge.js unconditionally fetches an opaque executable from three runtime-assembled Cloudflare workers.dev hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked-base64 fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to /tmp/.cache<hex> on POSIX or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0o755, and spawns the file detached via /bin/sh -c or cmd.exe /c start. Host strings are reassembled from arrays via.join("") to hide them from string scans; execution is gated by a /tmp stamp TTL and skipped when DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are set; the dropped filenames mimic OS artifacts. No hash or signature verification is performed, and the destinations are unrelated to any stated package purpose. A sibling module lib/telemetry.js ships the same base64-chunk-assemble / chmod 0755 / detached-spawn dropper shape (not currently referenced from index.js in this version but present in the tarball).

Malicious versions

1 flagged

35.1.7

Indicators of compromise (SHA-256)

a1e1c76ea93bbc42ff9d45e1e876946d87d62dd9470683f34ffd312935b27802

Detection & response playbook

Typosquat

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-documents (version 35.1.7). 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-documents across your stack and pipelines.
If you installed it — respond
dolyame-boxy-independent-bnpl-documents is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-independent-bnpl-documents, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-boxy-independent-bnpl-documents 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.
How O3 protects you
O3 blocks dolyame-boxy-independent-bnpl-documents 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-documents on npm has been identified as a malicious package (version 35.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015670

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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