Malicious Code Vulnerability in apollo-blaze-rate-limiter-vega Package
Summary
MAL-2025-139496: Malicious code in apollo-blaze-rate-limiter-vega (npm). Affected versions are not published. 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 apollo-blaze-rate-limiter-vega package is part of the npm ecosystem, designed to provide rate limiting functionality for applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms. This package, like others in the campaign, is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability originates from the package's involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of applications relying on this package. The malicious payload is designed to execute autopublish scripts that automate these harmful actions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall apollo-blaze-rate-limiter-vegaIf 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, you can prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your package-lock.json file does not include apollo-blaze-rate-limiter-vega. You can also use the following command to audit your dependencies: npm audit.
Conclusion
The apollo-blaze-rate-limiter-vega package has been identified as part of a malicious campaign that modifies package metadata and repackages it for nefarious purposes. It is crucial for developers to remove this package from their projects and utilize trusted alternatives to ensure the security of their applications.
See every vulnerability recorded for apollo-blaze-rate-limiter-vega →
FAQ
The malicious code can lead to the pollution of the npm registry and compromise the integrity of applications that depend on this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command npm uninstall apollo-blaze-rate-limiter-vega and replace it with a trusted alternative.
No patch is available for the apollo-blaze-rate-limiter-vega package as it is part of a malicious campaign. The best course of action is to remove it.
Regularly audit your dependencies using npm audit, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.