Critical Malicious Code Vulnerability in artifact-registry-client Package
Summary
MAL-2025-5893: Malicious code in artifact-registry-client (npm). Affects artifact-registry-client versions 99.99.99. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The artifact-registry-client is an npm package designed for interacting with artifact registries, enabling developers to manage and retrieve artifacts efficiently. However, this package has been identified to contain embedded malicious code, posing significant security risks to systems utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of malicious code embedded within the artifact-registry-client package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system running this package as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall artifact-registry-clientIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
Currently, the only effective workaround is to uninstall the artifact-registry-client package. You can do this by running the following command in your terminal: npm uninstall artifact-registry-client. Additionally, monitor your systems for any signs of compromise.
Conclusion
The artifact-registry-client package has been identified as containing malicious code, which poses severe security risks. Users must take immediate action to remove the package and secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for artifact-registry-client →
FAQ
Immediately uninstall the package and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Failing to address this vulnerability could lead to unauthorized access to sensitive data and complete compromise of the affected system.
As of now, there is no patched version available. Users should focus on removing the package entirely.
No, it is highly recommended to uninstall the package immediately, as it poses a significant security risk.
