Critical Malicious Code Vulnerability in @silgi/ratelimit Package

@silgi/ratelimit Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191318: Malicious code in @silgi/ratelimit (npm). Affects @silgi/ratelimit versions 0.2.1. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @silgi/ratelimit package is an npm library designed to help developers implement rate limiting in their applications. It provides functionality to control the number of requests a user can make to a service within a specified timeframe. However, this package has been compromised, leading to severe security implications for users who have integrated it into their projects.

Vulnerability Detail

The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infected the @silgi/ratelimit package. This malicious code is designed to steal sensitive tokens and credentials from users and subsequently publish them to GitHub. Furthermore, the worm can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. There is also a risk that the worm may destroy the user's home directory, leading to data loss.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @silgi/ratelimit

If 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 remove the @silgi/ratelimit package from their project by executing: npm uninstall @silgi/ratelimit. This will prevent the malicious code from executing until a safe version is available.

Conclusion

The @silgi/ratelimit package has been compromised by a malicious worm that poses significant risks to users. Immediate action is required to mitigate these risks, including updating or removing the package. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @silgi/ratelimit →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive tokens and credentials from users and publish them to GitHub.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

You should immediately uninstall the @silgi/ratelimit package and monitor your system for any unauthorized access or changes.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

Failure to address this vulnerability could lead to unauthorized access to sensitive information, data loss, and further propagation of the malicious code.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @silgi/ratelimit

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback