Malicious Code Injection in apollo-jest-titan-meteor: A Threat to npm Users
Summary
MAL-2025-139518: Malicious code in apollo-jest-titan-meteor (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
Apollo-jest-titan-meteor is an npm package that is part of the tea.xyz token reward campaign. This package is designed to assist developers in testing their Apollo-based applications. However, it has been compromised, making it susceptible to malicious code injections that can affect the integrity of the npm registry and the applications relying on it.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the apollo-jest-titan-meteor package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to the npm registry, leading to pollution and potential exploitation by attackers. The ramifications include compromised developer reputation scores and the risk of unintentional use of malicious packages by developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall apollo-jest-titan-meteorIf 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 remove the affected package from your project by executing the command: npm uninstall apollo-jest-titan-meteor. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The apollo-jest-titan-meteor package has been compromised with malicious code that poses significant risks to developers and their applications. It is crucial to update or remove the affected package and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive can help mitigate these risks.
See every vulnerability recorded for apollo-jest-titan-meteor →
FAQ
The malicious code modifies package.json files to remove private flags and generates random package names, which can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Using the compromised package can lead to security vulnerabilities in your application, including the risk of executing malicious code and damaging your project's integrity.
Regularly update your dependencies and utilize tools like Vulert to monitor your packages for vulnerabilities. Always review the packages you include in your projects.
If you have already used the compromised package, uninstall it immediately and check your application for any signs of compromise. Update to a secure version as soon as it becomes available.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.