Which versions of egair0810 are malicious?

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

How do I remediate egair0810 if I installed it?

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

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

Yes — egair0810 is associated with the GHSA-5vqp-mfpc-2j65, IN-MAL-2026-017473, IN-MAL-2026-017474 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 egair0810 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 egair0810 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging egair0810 across your stack and pipelines.

Malicious package

egair0810npm

egair0810 is a confirmed malicious npm package (MAL-2026-13805) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in egair0810 (npm)

MAL-2026-13805

Immediate action

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

npm uninstall egair0810

What this malware does

The package contains a single index.html file declared as the package main, presenting a fake 'Just a moment...' / Cloudflare Turnstile page with heavily obfuscated JavaScript (string-array + shuffling style) that constructs a target URL from encoded strings and calls window.location.replace to redirect the browser. package.json declares no preinstall, install, postinstall, or prepare lifecycle scripts, and main points at an HTML file that Node cannot load as a module, so npm install and require() of the package do not execute the obfuscated code. The payload only runs if the HTML is opened in a browser. The artifact is not a functioning npm library and appears to be registry abuse hosting a browser-facing redirect/phishing lure 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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

4bfa32efc211e2ddab756898b2eb924cc6667f2a94adcd88850ba53d5c9c2067

1c3e0c6182d502b74ddae5a2993e3096f82e00211bab173a12ac799406a3e5e5

2778f49499126b52d7dc9bbf728ed62bc8177ea325300c7907f2a4b854436507

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

Campaign

GHSA-5vqp-mfpc-2j65IN-MAL-2026-017473IN-MAL-2026-017474

References

Credits

Amazon Inspector · finder

Detect & block this

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