Malicious Code Detected in equests Package - Security Alert

equests Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19733: Malicious code in equests (npm). Affected versions are not published. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The equests package is a Node.js library designed to simplify HTTP requests, providing an easy-to-use interface for making network calls. It is commonly used in various applications for its convenience and efficiency. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the equests package stems from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this library. This code can lead to unauthorized access, data breaches, and other harmful actions within the affected systems. The malicious behavior was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall equests

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 implement security measures such as monitoring network traffic and employing application firewalls to detect and block any suspicious activities related to the equests package. Additionally, consider using alternative libraries for making HTTP requests, such as axios or node-fetch.

Conclusion

The discovery of malicious code in the equests package poses a serious threat to users and their applications. Immediate action is required to mitigate risks by removing the package and considering secure alternatives. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time.

See every vulnerability recorded for equests →

Share this vulnerability

FAQ

equests is a Node.js library that simplifies making HTTP requests, providing an easy interface for developers.

The malicious code can lead to unauthorized access and data breaches, compromising the security of applications using the 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.

It is recommended to remove the equests package and replace it with a secure alternative, as there is no patched version available at this time.

Yes, consider using libraries like axios or node-fetch for making HTTP requests securely.

Related vulnerabilities

Recent vulnerabilities recorded for equests.

How To Fix

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

npm uninstall equests

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