Which versions of 0xegg2024 are malicious?

The following npm versions of 0xegg2024 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate 0xegg2024 if I installed it?

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

If 0xegg2024 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is 0xegg2024 part of a known attack campaign?

Yes — 0xegg2024 is associated with the IN-MAL-2026-002467 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 0xegg2024 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 0xegg2024 (version 1.0.2).

Malicious package

0xegg2024npm

Advisory published May 12, 2026Updated May 13, 2026

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

Malicious code in 0xegg2024 (npm)

MAL-2026-3668

Immediate action

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

npm uninstall 0xegg2024

What this malware does

Tea.yaml token farming campaign

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

86f32380998652e4d6d7b70da165cff6d669a4c6a6d9297da2a137071abf6317

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for 0xegg2024 (version 1.0.2).
If you installed it — respond
Remove 0xegg2024 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 0xegg2024 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. 0xegg2024 on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002467

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 0xegg2024-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