Which versions of @f5rest/odata-v4-metadata are malicious?

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

How do I remediate @f5rest/odata-v4-metadata if I installed it?

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

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

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

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

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

Malicious package

@f5rest/odata-v4-metadatanpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@f5rest/odata-v4-metadata is a confirmed malicious npm package (MAL-2026-1620) 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/odata-v4-metadata (npm)

MAL-2026-1620

Immediate action

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

npm uninstall @f5rest/odata-v4-metadata

What this malware does

The package @f5rest/odata-v4-metadata was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

6a10a71dd22dfe3aaee77188579a8a168a1d9b3335089d0c724727f7aeef303e

6b451b98b071a1d7cb27b5486b71503e5611d52b987a3ded3f6ec15b556ce453

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @f5rest/odata-v4-metadata-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