What does the bnpl-blocks-independent-bnpl-features malware do?

On require() of the package, index.js loads./_bridge.js which reconstructs attacker-controlled hostnames from split string fragments (oob-worker.cf10*.workers.dev, with a DNS TXT fallback via *.wel1.ru) using.join(''), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name resembling dotnet_diag_ .exe or.cache_ , chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Execution is gated only by a mtime stamp file and a DISABLE_TELEMETRY-style env var. A DNS-TXT chunked-transfer channel base64-reassembles payload bytes as a fallback when HTTPS is blocked. Comments frame the behavior as 'telemetry'/'analytics'. Hostna

Which versions of bnpl-blocks-independent-bnpl-features are malicious?

The following npm versions of bnpl-blocks-independent-bnpl-features are flagged malicious: 35.7.2. Treat any of these as compromised.

How do I remediate bnpl-blocks-independent-bnpl-features if I installed it?

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

If bnpl-blocks-independent-bnpl-features 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.

Is bnpl-blocks-independent-bnpl-features part of a known attack campaign?

Yes — bnpl-blocks-independent-bnpl-features is associated with the IN-MAL-2026-015430 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-independent-bnpl-features across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-features (version 35.7.2).

Malicious package

bnpl-blocks-independent-bnpl-featuresnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in bnpl-blocks-independent-bnpl-features (npm)

MAL-2026-12956

Immediate action

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

npm uninstall bnpl-blocks-independent-bnpl-features

What this malware does

On require() of the package, index.js loads./bridge.js which reconstructs attacker-controlled hostnames from split string fragments (oob-worker.cf10*.workers.dev, with a DNS TXT fallback via *.wel1.ru) using.join(''), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name resembling dotnet_diag<rand>.exe or.cache_<rand>, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Execution is gated only by a mtime stamp file and a DISABLE_TELEMETRY-style env var. A DNS-TXT chunked-transfer channel base64-reassembles payload bytes as a fallback when HTTPS is blocked. Comments frame the behavior as 'telemetry'/'analytics'. Hostname reconstruction, disguised filename, detached spawn, and DNS-based delivery are deliberate evasion patterns rather than misconfiguration.

Malicious versions

1 flagged

35.7.2

Indicators of compromise (SHA-256)

afeff40a463b598ac2764623ad9820714953bbb4a882848e4a2d68d1ec0a74fd

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-features (version 35.7.2).
If you installed it — respond
bnpl-blocks-independent-bnpl-features 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-independent-bnpl-features 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-independent-bnpl-features on npm has been identified as a malicious package (version 35.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015430

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-independent-bnpl-features-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