Malicious Code Detected in express-ycsrf Package

express-ycsrf Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20094: Malicious code in express-ycsrf (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The express-ycsrf package is a Node.js middleware designed to provide CSRF protection for Express applications. It helps developers secure their web applications by ensuring that requests are coming from authenticated users. However, recent findings have revealed that this package contains malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The express-ycsrf package has been identified to contain malicious code that could compromise the security of applications using it. This vulnerability originated from the package itself, which was found to have been tampered with, potentially allowing attackers to execute arbitrary code or steal sensitive information from users. The implications of this vulnerability are severe, as it can lead to unauthorized access and data breaches.

How To Fix

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

npm uninstall express-ycsrf

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, you can disable the use of express-ycsrf in your application until a secure version is released. This can be done by commenting out or removing the middleware from your Express app configuration.

Conclusion

The discovery of malicious code in the express-ycsrf package highlights the importance of regularly auditing dependencies in software projects. Developers should take immediate action to remove the affected package and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for express-ycsrf →

Share this vulnerability

FAQ

express-ycsrf is a middleware for Node.js that provides CSRF protection for Express applications.

The malicious code was discovered through security audits and reports from security researchers.

Using the compromised package can lead to unauthorized access, data breaches, and exploitation of user information.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

It is advisable to remove the express-ycsrf package immediately and replace it with a secure alternative.

How To Fix

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

npm uninstall express-ycsrf

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