Which versions of elemefe are malicious?

The following npm versions of elemefe are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate elemefe if I installed it?

elemefe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed elemefe — how do I know if it already compromised me?

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

Yes — elemefe is associated with the GHSA-8q39-fjr6-f9v2, RLMA-2025-05774 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 elemefe across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for elemefe (version 99.0.0).

Malicious package

elemefenpm

Advisory published Oct 29, 2025Updated Dec 2, 2025

elemefe is a confirmed malicious npm package (MAL-2025-48995) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in elemefe (npm)

MAL-2025-48995

Immediate action

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

npm uninstall elemefe

What this malware does

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.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

fcbb1237331b1e8b0d21101d938aba8142d3d16132e181b92f0a2d91b389e90d

bce643418ca7557d0b7de22ffd4e25e255c713d8f5345b2c8b908b1afcc94285

662cfc4fca3b67a11e9c45ab8fde867758d5b64bd8f5fd005542eacf216262cc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for elemefe (version 99.0.0).
If you installed it — respond
elemefe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If elemefe 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. elemefe on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8q39-fjr6-f9v2RLMA-2025-05774

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks elemefe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database