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

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

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

dolyame-boxy-independent-bnpl-cards is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If dolyame-boxy-independent-bnpl-cards 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-cards part of a known attack campaign?

Yes — dolyame-boxy-independent-bnpl-cards is associated with the IN-MAL-2026-015681 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-cards 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-cards (version 35.7.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-cards across your stack and pipelines.

Malicious package

dolyame-boxy-independent-bnpl-cardsnpm

dolyame-boxy-independent-bnpl-cards is a confirmed malicious npm package (MAL-2026-13314) that steals credentials and exfiltrates sensitive data (malicious version 35.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-13314

Immediate action

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

npm uninstall dolyame-boxy-independent-bnpl-cards

What this malware does

On import, index.js requires setup.js, which downloads an opaque binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT covert-channel fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The payload is written to /tmp or %TEMP% under a disguised name (dotnet_diag_<uid>.exe on Windows,.cache_<uid> on Unix), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. There is no hash or signature verification, hostnames are assembled from array fragments joined at runtime, and the download destinations are unrelated to the package's stated BNPL-cards purpose. A lockfile named.analytics_state and opt-out env vars named DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are used as a telemetry cover story.

Malicious versions

1 flagged

35.7.6

Indicators of compromise (SHA-256)

5b2211179bcef10cb641d7ad848be2a71a3048d90108c4651b471ba60404f2d2

Detection & response playbook

Credential / info stealer

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-cards (version 35.7.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-cards across your stack and pipelines.
If you installed it — respond
dolyame-boxy-independent-bnpl-cards is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-boxy-independent-bnpl-cards 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-cards 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-cards on npm has been identified as a malicious package (version 35.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015681

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database