Which versions of egypt0811 are malicious?

The following npm versions of egypt0811 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate egypt0811 if I installed it?

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

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

Yes — egypt0811 is associated with the GHSA-h37q-gcmq-hv56, IN-MAL-2026-017441 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 egypt0811 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 egypt0811 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging egypt0811 across your stack and pipelines.

Malicious package

egypt0811npm

egypt0811 is a confirmed malicious npm package (MAL-2026-13806) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in egypt0811 (npm)

MAL-2026-13806

Immediate action

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

npm uninstall egypt0811

What this malware does

The package contains only index.html (declared as main) with no JavaScript modules, no lifecycle scripts (preinstall/install/postinstall), and no bin entries. The HTML is styled as a Cloudflare Turnstile 'Just a moment...' interstitial and contains an obfuscated inline script that reconstructs a destination URL beginning with 'https://eg' from a string-array and calls window.location.replace to redirect the visitor's browser, forwarding query parameters. Neither npm install nor Node require() of this package executes any code — HTML is not a Node module and no install-time hooks are declared. The redirect fires only if a browser opens the HTML file directly. This looks like registry abuse to host a phishing/redirect page rather than a supply-chain attack against developers who install the package.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1b6be4ff83c32ab5150e10cd1084cdd48f2ef23b8a7470a5928379acd7eccc55

77d31e1b5baa802662cbb61387f5c3b759d159e74e8776d9515198db5c168074

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

Campaign

GHSA-h37q-gcmq-hv56IN-MAL-2026-017441

References

Credits

Amazon Inspector · finder

Detect & block this

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