Which versions of metadata-lib are malicious?

The following npm versions of metadata-lib are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate metadata-lib if I installed it?

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

If metadata-lib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is metadata-lib part of a known attack campaign?

Yes — metadata-lib is associated with the GHSA-hg73-hr7x-6cp6, RLMA-2025-05429, RLUA-2025-05888 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 metadata-lib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metadata-lib (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metadata-lib across your stack and pipelines.

Malicious package

metadata-libnpm

metadata-lib is a confirmed malicious npm package (MAL-2025-47999) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in metadata-lib (npm)

MAL-2025-47999

Immediate action

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

npm uninstall metadata-lib

What this malware does

The package communicates with a domain associated with malicious activity.

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.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

2c93e5bf4059b5ffebc879cdbf901fc2a8508bf82f03b69abfd0ca6e9681aee8

68e3d50f21d0d03ccf7de79695b5b8ed7a6099f8ae6df4f352bbece6003c3ecc

f6ff9b9101268fa8878d0c2374d2cb8fc6c80041d3c8f7f94f60f4255ea574d2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for metadata-lib (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metadata-lib across your stack and pipelines.
If you installed it — respond
Remove metadata-lib 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 metadata-lib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks metadata-lib before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-hg73-hr7x-6cp6RLMA-2025-05429RLUA-2025-05888

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks metadata-lib-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