Which versions of bismillahitidakimas are malicious?

The following npm versions of bismillahitidakimas are flagged malicious: 1.1.2, 2.0.0. Treat any of these as compromised.

How do I remediate bismillahitidakimas if I installed it?

Remove bismillahitidakimas 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 bismillahitidakimas — how do I know if it already compromised me?

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

Yes — bismillahitidakimas is associated with the GHSA-wxph-qcjv-r95v, IN-MAL-2026-010447, RLMA-2026-05500, RLUA-2026-06086 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 bismillahitidakimas 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 bismillahitidakimas (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bismillahitidakimas across your stack and pipelines.

Malicious package

bismillahitidakimasnpm

bismillahitidakimas is a confirmed malicious npm package (MAL-2026-10295) that executes malicious code on install (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bismillahitidakimas (npm)

MAL-2026-10295

Immediate action

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

npm uninstall bismillahitidakimas

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.1.22.0.0

Indicators of compromise (SHA-256)

dee41a87f2cd0040ad02da601dcf2159a5954d62cac918740f17b7c65f304bee

fbdeeb9f66b286397502ebf5d67dacf17f4cc4f58917fa9d201d799bb99c3e2c

03e11ce129c787639fcd1410e074ac1eca85c00dc5650e1ae198d03ab8c24ea3

5d10c14d8a27b8e7232b1d287629245b952e22b1d81c728f28da0904504e239f

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

Campaign

GHSA-wxph-qcjv-r95vIN-MAL-2026-010447RLMA-2026-05500RLUA-2026-06086

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks bismillahitidakimas-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