Malicious Code Vulnerability in google-audit-tool: Security Risk Identified
Summary
MAL-2026-1742: Malicious code in google-audit-tool (npm). Affects google-audit-tool versions 1.0.0 – 1.0.1. 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 google-audit-tool is an npm package designed to assist developers in auditing their applications for vulnerabilities. It provides a user-friendly interface and integrates with various tools to enhance security practices. However, recent findings have revealed that certain versions of this package contain malicious code, posing a significant risk to users who rely on it for secure application development.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code in versions 1.0.0 and 1.0.1 of the google-audit-tool package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The origin of this vulnerability has been traced back to a malicious actor who injected harmful code into the package, which was subsequently published to the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall google-audit-toolIf 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
As a temporary workaround, users can avoid using the affected versions (1.0.0 and 1.0.1) of the google-audit-tool package. Instead, consider using alternative auditing tools or manually auditing your application until a secure version is confirmed.
Conclusion
The discovery of malicious code in the google-audit-tool package highlights the importance of regularly auditing and updating dependencies in software development. Users are strongly advised to update to the latest version of the package and consider using tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for google-audit-tool →
FAQ
Versions 1.0.0 and 1.0.1 of the google-audit-tool package are affected by this vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without any signup.
If an immediate update is not possible, consider using alternative tools for auditing or manually checking your application for vulnerabilities.
Yes, continuing to use the affected versions poses a risk of unauthorized access and potential data breaches.
The vulnerability was discovered by ReversingLabs, a security research firm specializing in malware analysis.
