Which versions of bnpl-blocks-mobile-bnpl-notification are malicious?

The following npm versions of bnpl-blocks-mobile-bnpl-notification are flagged malicious: 35.5.6. Treat any of these as compromised.

How do I remediate bnpl-blocks-mobile-bnpl-notification if I installed it?

bnpl-blocks-mobile-bnpl-notification 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 bnpl-blocks-mobile-bnpl-notification — how do I know if it already compromised me?

If bnpl-blocks-mobile-bnpl-notification 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 bnpl-blocks-mobile-bnpl-notification part of a known attack campaign?

Yes — bnpl-blocks-mobile-bnpl-notification is associated with the IN-MAL-2026-015381 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 bnpl-blocks-mobile-bnpl-notification 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 bnpl-blocks-mobile-bnpl-notification (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-notification across your stack and pipelines.

Malicious package

bnpl-blocks-mobile-bnpl-notificationnpm

bnpl-blocks-mobile-bnpl-notification is a confirmed malicious npm package (MAL-2026-12999) that steals credentials and exfiltrates sensitive data (malicious version 35.5.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-mobile-bnpl-notification (npm)

MAL-2026-12999

Immediate action

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

npm uninstall bnpl-blocks-mobile-bnpl-notification

What this malware does

index.js requires./setup on module load. setup.js assembles Cloudflare Workers hostnames from split string fragments (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT base64 fallback under *.dl.wel1.ru, downloads a platform-specific binary via https.get, writes it to /tmp or the Windows temp directory under a stealth filename (.cache_<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and detach-spawns it via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are obfuscated by string-split concatenation and the code carries cover-story identifiers (analytics_state, DISABLE_TELEMETRY, User-Agent 'node-fetch/2.6'). lib/telemetry.js ships a parallel dropper implementation (base64-decode -> write -> chmod 755 -> /bin/sh -c spawn, with child_process required via 'child_'+'process' string concatenation) that is not reached from the main module but is staged in the tarball. The package's stated purpose is a mobile SDK; the shipped code instead performs unpinned, unverified remote binary execution on the installer's host.

Malicious versions

1 flagged

35.5.6

Indicators of compromise (SHA-256)

d66362455002e754cf596122aa451dcd28d20d3a446b5284d2be76d8db6af4cb

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 bnpl-blocks-mobile-bnpl-notification (version 35.5.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-notification across your stack and pipelines.
If you installed it — respond
bnpl-blocks-mobile-bnpl-notification 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 bnpl-blocks-mobile-bnpl-notification 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 bnpl-blocks-mobile-bnpl-notification 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. bnpl-blocks-mobile-bnpl-notification on npm has been identified as a malicious package (version 35.5.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015381

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-mobile-bnpl-notification-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