NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bnpl-blocks-atom-bnpl-skeletonnpm

Advisory published Updated

bnpl-blocks-atom-bnpl-skeleton is a confirmed malicious npm package (MAL-2026-12893) that executes malicious code on install (malicious version 35.6.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-skeleton (npm)

MAL-2026-12893
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-atom-bnpl-skeleton

What this malware does

On require of the package's main entry, init.js fetches a platform-specific binary from obfuscated Cloudflare Workers hostnames (assembled by joining split substrings, e.g. oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT chunked-base64 fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised filenames (dotnet_diag<token>.exe on Windows,.cache_<token> on Unix), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe. No source, hash, or signature is verified. A parallel dropper bundle in lib/telemetry.js replicates the same write-chmod-spawn primitive behind an analytics/telemetry cover story, with additional string-splitting obfuscation of sensitive APIs (require("child_"+"process"), fs["chmod"+"Sync"]). Any consumer importing this package executes arbitrary attacker-controlled native code on the host.

Malicious versions

1 flagged
35.6.3

Indicators of compromise (SHA-256)

d2e88e9faf590414055ba1b7b48bdaa51df5e33735b9dd526e5d8d0650eceae7

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-skeleton (version 35.6.3).

  2. If you installed it — respond

    Remove bnpl-blocks-atom-bnpl-skeleton 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-atom-bnpl-skeleton was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bnpl-blocks-atom-bnpl-skeleton on npm has been identified as a malicious package (version 35.6.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015482

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-skeleton-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-atom-bnpl-skeleton (npm) malicious package — MAL-2026-12893 | O3 Security