Which versions of bnpl-blocks-atom-bnpl-skeleton are malicious?

The following npm versions of bnpl-blocks-atom-bnpl-skeleton are flagged malicious: 35.6.3. Treat any of these as compromised.

How do I remediate bnpl-blocks-atom-bnpl-skeleton if I installed it?

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

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

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

Malicious package

bnpl-blocks-atom-bnpl-skeletonnpm

bnpl-blocks-atom-bnpl-skeleton is a confirmed malicious npm package (MAL-2026-12893) that steals credentials and exfiltrates sensitive data (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

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-atom-bnpl-skeleton (version 35.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-skeleton across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-skeleton 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-atom-bnpl-skeleton 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-atom-bnpl-skeleton 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-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

npmjs.com

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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database