Which versions of howmanygreatbritain are malicious?

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

How do I remediate howmanygreatbritain if I installed it?

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

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

Yes — howmanygreatbritain is associated with the GHSA-fqc5-3x3h-cwmh, IN-MAL-2026-010443, RLMA-2026-05555, RLUA-2026-06272 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 howmanygreatbritain 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 howmanygreatbritain (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging howmanygreatbritain across your stack and pipelines.

Malicious package

howmanygreatbritainnpm

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

MAL-2026-10304

Immediate action

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

npm uninstall howmanygreatbritain

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)

1b90c6452504427b0e611f69e5aa56be62fc07805335c78c8b7b6e7674036726

66707a972e4b6d232236d552157967ca09de229587cb90ca80ab1a1cac83fd22

dcef543b271c2e2d0bf834d0d02f744d28f6eaddfa199c474f4f4ce39189df0f

e7944879e969eafba650f162229e41f2d2ea225984100a1e8d20488da12986cb

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 howmanygreatbritain (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging howmanygreatbritain across your stack and pipelines.
If you installed it — respond
Remove howmanygreatbritain 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 howmanygreatbritain 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 howmanygreatbritain 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. howmanygreatbritain 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-fqc5-3x3h-cwmhIN-MAL-2026-010443RLMA-2026-05555RLUA-2026-06272

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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