Critical Malicious Code Vulnerability in revenuecat Package
Summary
MAL-2025-191418: Malicious code in revenuecat (npm). Affects revenuecat versions 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 revenuecat package is a popular npm library used for managing in-app subscriptions and purchases in mobile applications. It provides developers with tools to integrate subscription management seamlessly into their apps. However, this package has been compromised, making it susceptible to severe security threats.
Vulnerability Detail
The vulnerability stems from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from the user's environment and publish them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The potential ramifications include complete compromise of the user's system, loss of sensitive information, and possible destruction of the user's home directory.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall revenuecatIf 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 measure, you can prevent the execution of the compromised package by uninstalling it with the following command: npm uninstall revenuecat. However, be aware that removing the package may not eliminate all malicious software that has already been installed.
Conclusion
The revenuecat package has been compromised by a malicious worm that poses significant security risks. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor their applications for vulnerabilities.
See every vulnerability recorded for revenuecat →
FAQ
Immediately uninstall the revenuecat package and rotate any secrets or keys stored on the affected machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failure to address this vulnerability can lead to unauthorized access to sensitive information, potential data loss, and complete compromise of your system.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.
It is advisable to avoid using the revenuecat package until a secure, patched version is released and you have verified its safety.
