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

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

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

Remove bnpl-blocks-independent-bnpl-cards 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.

I already installed bnpl-blocks-independent-bnpl-cards — how do I know if it already compromised me?

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

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

Malicious package

bnpl-blocks-independent-bnpl-cardsnpm

bnpl-blocks-independent-bnpl-cards is a confirmed malicious npm package (MAL-2026-12952) that executes malicious code on install (malicious version 35.5.3). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12952

Immediate action

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

npm uninstall bnpl-blocks-independent-bnpl-cards

What this malware does

On require of the package, index.js loads bridge.js which reconstructs attacker-controlled hostnames via array.join("") string splits (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, with a DNS-TXT chunked base64 fallback via *.sdk.dl.wel1.ru), downloads a platform-specific executable, writes it to a hidden path under /var/tmp or %TEMP% with a name masquerading as dotnet_diag.exe or.cache_, chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe with.unref(). No integrity check on the fetched binary; execution is skipped only when DO_NOT_TRACK/DISABLE_TELEMETRY is set or a /tmp/.analytics_state marker file exists. Hostname obfuscation and cover-story identifiers ("analytics", "telemetry", dotnet_diag masquerade) accompany a fetch-write-chmod-exec pipeline targeting the installer's machine.

Malicious versions

1 flagged

35.5.3

Indicators of compromise (SHA-256)

063ad90855d7ee9b794ccc1e32a794000434fb6955e82152a4d4118ff8e3e266

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-independent-bnpl-cards (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-independent-bnpl-cards across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-cards 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-independent-bnpl-cards 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-independent-bnpl-cards 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-independent-bnpl-cards on npm has been identified as a malicious package (version 35.5.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015433

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database