Which versions of @f5rest/icr-metadata-generator are malicious?

The following npm versions of @f5rest/icr-metadata-generator are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @f5rest/icr-metadata-generator if I installed it?

Remove @f5rest/icr-metadata-generator 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 @f5rest/icr-metadata-generator — how do I know if it already compromised me?

If @f5rest/icr-metadata-generator 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 @f5rest/icr-metadata-generator part of a known attack campaign?

Yes — @f5rest/icr-metadata-generator is associated with the RLMA-2026-00998 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 @f5rest/icr-metadata-generator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @f5rest/icr-metadata-generator (version 99.0.0).

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

Malicious package

@f5rest/icr-metadata-generatornpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@f5rest/icr-metadata-generator is a confirmed malicious npm package (MAL-2026-1616) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @f5rest/icr-metadata-generator (npm)

MAL-2026-1616

Immediate action

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

npm uninstall @f5rest/icr-metadata-generator

What this malware does

The package @f5rest/icr-metadata-generator was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

46f15a5e51cf25b333b71e7653934d7c8326c4b51b8cc46d6013a5e33643d80a

997e0d3cb7fd000b08e52b7679e870d2ade8d698b16aeec6f2497aae10bea376

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @f5rest/icr-metadata-generator (version 99.0.0).
If you installed it — respond
Remove @f5rest/icr-metadata-generator 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 @f5rest/icr-metadata-generator 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. @f5rest/icr-metadata-generator 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

RLMA-2026-00998

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @f5rest/icr-metadata-generator-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