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

bnpl-blocks-mobile-bnpl-card-gallerynpm

bnpl-blocks-mobile-bnpl-card-gallery is a confirmed malicious npm package (MAL-2026-12982) that executes malicious code on install (malicious version 35.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-mobile-bnpl-card-gallery (npm)

MAL-2026-12982
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-mobile-bnpl-card-gallery

What this malware does

On require of the package, index.js loads./vendor.js, which assembles Cloudflare Workers hostnames from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback pointing at sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. It downloads a per-platform binary via https.get, writes it to a temporary path under a disguised name (dotnet_diag.exe /.cache_), chmods it 755, and spawns it detached via /bin/sh or cmd. child_process and chmodSync are referenced through concatenated identifiers ('child_'+'process', 'chmod'+'Sync') to evade static analysis. No hash or signature verification is performed, the destinations are unrelated to any device-integration or card-gallery purpose, and the disguise, obfuscation, and covert DNS-TXT channel indicate hostile intent.

Malicious versions

1 flagged
35.4.3

Indicators of compromise (SHA-256)

9c54195f215860087ea60839eed874351de1bf279c7a80d12c128214d3602b26

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 bnpl-blocks-mobile-bnpl-card-gallery (version 35.4.3). 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-card-gallery across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015403

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

bnpl-blocks-mobile-bnpl-card-gallery (npm) malicious package — MAL-2026-12982 | O3 Security