Which versions of bnpl-blocks-scroll are malicious?

The following npm versions of bnpl-blocks-scroll are flagged malicious: 35.2.6. Treat any of these as compromised.

How do I remediate bnpl-blocks-scroll if I installed it?

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

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

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

Malicious package

bnpl-blocks-scrollnpm

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

Malicious code in bnpl-blocks-scroll (npm)

MAL-2026-13015

Immediate action

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

npm uninstall bnpl-blocks-scroll

What this malware does

On require() of bnpl-blocks-scroll, index.js loads helpers.js, which selects a platform-specific payload path and fetches an opaque native executable via https.get from one of three Cloudflare Workers hosts whose names are assembled at runtime by joining string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev). If the HTTPS mirrors fail, the code reconstructs the payload from base64-encoded DNS TXT records under a platform-specific subdomain of wel1.ru (dns.resolveTxt on c.<domain>, resolvers themselves assembled by [].join('')). The retrieved bytes are written to /tmp or %TEMP% under disguised names (.cache<hex> on unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, then spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() or spawn('cmd',...). A.analytics_state cooldown file and honoring of DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env vars provide a telemetry cover story that does not match the actual behavior (fetching and executing an unpinned, unverified native binary). Host-name string-splitting, DNS-over-TXT fallback transport, cover-story filenames, and detached execution together constitute a deliberate remote-code-execution dropper against any machine that installs or imports this package.

Malicious versions

1 flagged

35.2.6

Indicators of compromise (SHA-256)

99a0a2e3786f50dc07b4546de5ae22f3a65ad50e95897b8ca4d0fa6460b32d63

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

Campaign

IN-MAL-2026-015369

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-scroll-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