Which versions of @fdfe/era-build are malicious?

The following npm versions of @fdfe/era-build are flagged malicious: 1.0.15. Treat any of these as compromised.

How do I remediate @fdfe/era-build if I installed it?

Remove @fdfe/era-build 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 @fdfe/era-build — how do I know if it already compromised me?

If @fdfe/era-build 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 @fdfe/era-build part of a known attack campaign?

Yes — @fdfe/era-build is associated with the RLMA-2024-00073, RLUA-2024-05923 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 @fdfe/era-build across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @fdfe/era-build (version 1.0.15).

Part of a larger attack: @fdfe published 10 malicious packages. See the full campaign →

Malicious package

@fdfe/era-buildnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@fdfe/era-build is a confirmed malicious npm package (MAL-2024-2310) that executes malicious code on install (malicious version 1.0.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fdfe/era-build (npm)

MAL-2024-2310

Immediate action

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

npm uninstall @fdfe/era-build

Malicious versions

1 flagged

1.0.15

Indicators of compromise (SHA-256)

a9ce332378ad2463198663441ed6f84ce13768ab8ab843b394fd5a8f4d576a3e

71d1a4c895a844a96fa069fdc8bcb72c98810a41844cb8a772bf95eff5726bce

fbf957f36cabc8c27e7114ca0f3e7b21367f63d1448e160e72f1278ee3e3b1f9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @fdfe/era-build (version 1.0.15).
If you installed it — respond
Remove @fdfe/era-build 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 @fdfe/era-build 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. @fdfe/era-build on npm has been identified as a malicious package (version 1.0.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00073RLUA-2024-05923

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @fdfe/era-build-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