Which versions of thebigyahu are malicious?

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

How do I remediate thebigyahu if I installed it?

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

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

Yes — thebigyahu is associated with the GHSA-2hh4-hfw3-mgxv, IN-MAL-2026-010448, RLMA-2026-05632, RLUA-2026-06520 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 thebigyahu 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 thebigyahu (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging thebigyahu across your stack and pipelines.

Malicious package

thebigyahunpm

thebigyahu is a confirmed malicious npm package (MAL-2026-10387) 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 thebigyahu (npm)

MAL-2026-10387

Immediate action

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

npm uninstall thebigyahu

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)

b22605d5d9985e43c38bf72f8e8841d2d4defb289253fdf4783bb91f73fcb12f

3eb60a0e719514988070d96c3cedea8d918edccef68203afe3cda86635c607de

afcc7b72a335bae7a747577515262fdfe196e97b4375719bcc29930d0cf83fd4

9ab99ade52332524637882d9ad5e6c849d484fc79370ca092f01403e02b6312b

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 thebigyahu (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging thebigyahu across your stack and pipelines.
If you installed it — respond
Remove thebigyahu 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 thebigyahu 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 thebigyahu 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. thebigyahu 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-2hh4-hfw3-mgxvIN-MAL-2026-010448RLMA-2026-05632RLUA-2026-06520

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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