bnpl-blocks-mobile-bnpl-info-slidernpm
bnpl-blocks-mobile-bnpl-info-slider is a confirmed malicious npm package (MAL-2026-12995) that executes malicious code on install (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-info-slider (npm)
What this malware does
index.js unconditionally requires./setup.js when the module is loaded. setup.js selects a platform-specific payload for linux_x64, linux_arm64, darwin, or win32 and downloads it from Cloudflare Workers hostnames reconstructed at runtime via string-array joins (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT fallback on subdomains of dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Additional obfuscation is present: dynamic property assembly (fs["chmod"+"Sync"], require("child_"+"process")), a cover-story marker file named.analytics_state, and a sibling lib/telemetry.js that presents Sentry-like SDK comments while duplicating the dropper primitives. The package's declared purpose ("platform adapter") does not exist as functionality — index.js exports a trivial no-op class, package.json declares no dependencies, and the only substantive behavior is the dropper. Any consumer that require()s this package receives full-host code execution from attacker-controlled infrastructure.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-info-slider (version 35.8.4). 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-info-slider across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-info-slider 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.
Did it already run?
If bnpl-blocks-mobile-bnpl-info-slider 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-info-slider 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bnpl-blocks-mobile-bnpl-info-slider-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.