Critical Malicious Code Vulnerability in @trpc-rate-limiter/cloudflare Package
Summary
MAL-2025-191327: Malicious code in @trpc-rate-limiter/cloudflare (npm). Affects @trpc-rate-limiter/cloudflare versions 0.1.4. 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 @trpc-rate-limiter/cloudflare package is a Node.js library designed to provide rate limiting functionality for applications deployed on Cloudflare. It is commonly used to enhance application performance and security by controlling the number of requests a user can make in a given timeframe. However, this package has been compromised, leading to severe security implications for users who have it installed.
Vulnerability Detail
The vulnerability stems from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This malicious code is designed to steal tokens and credentials, publishing them to GitHub. It can also propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Furthermore, there is a risk that the worm could destroy the user's home directory, leading to significant data loss and system compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @trpc-rate-limiter/cloudflareIf 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 workaround, users should consider isolating their development environments and using containerization or virtual machines to minimize the risk of exposure to malicious packages. Additionally, ensure that sensitive data is not stored on machines with compromised packages.
Conclusion
The @trpc-rate-limiter/cloudflare package has been compromised, leading to severe security vulnerabilities that can affect users' systems and data. Immediate action is required to mitigate risks, including removing the package and rotating sensitive credentials. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.
See every vulnerability recorded for @trpc-rate-limiter/cloudflare →
FAQ
Immediately remove the 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 any signup.
The risks include credential theft, unauthorized access to your GitHub repositories, potential data loss, and full system compromise.
Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and ensure you are using trusted packages.
It is advisable to avoid using this package until it has been verified as secure and free from malicious code.
