Malicious Code Detected in faraday-statsd Package - Security Alert

faraday-statsd Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20222: Malicious code in faraday-statsd (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 faraday-statsd package is an npm library designed for integrating with the StatsD metrics server, allowing developers to send performance metrics from their applications. It is commonly used in Node.js applications to monitor and analyze performance data. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users who have integrated it into their projects.

Vulnerability Detail

The vulnerability in the faraday-statsd package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical 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 faraday-statsd

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 avoid using the faraday-statsd package and implement custom metrics reporting to StatsD using alternative libraries or direct HTTP requests to the StatsD server.

Conclusion

The discovery of malicious code in the faraday-statsd package poses a serious threat to users. It is essential to take immediate action by removing the package and replacing it with a secure alternative. Regular monitoring of dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for faraday-statsd →

Share this vulnerability

FAQ

faraday-statsd is an npm package used for sending metrics to the StatsD server, commonly utilized in Node.js applications for performance monitoring.

The malicious code was identified by security researchers from Amazon Inspector, who regularly monitor open-source packages for vulnerabilities.

Using the compromised faraday-statsd package can lead to unauthorized access to your application, data breaches, and potential exploitation by attackers.

You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can alert you in real-time about any vulnerabilities, including this one.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup or installation.

How To Fix

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

npm uninstall faraday-statsd

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