Critical Security Breach in @voiceflow/eslint-config: Malicious Code Detected

@voiceflow/eslint-config Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191345: Malicious code in @voiceflow/eslint-config (npm). Affects @voiceflow/eslint-config versions 7.16.4 – 7.16.5. 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 @voiceflow/eslint-config package is a configuration tool for ESLint, a popular JavaScript linter that helps developers identify and fix problems in their JavaScript code. This package is widely used in projects to maintain code quality and consistency. However, it has recently been compromised, exposing users to significant security risks.

Vulnerability Detail

The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from users and publish them to GitHub. It can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. Additionally, the worm has the potential to destroy the user's home directory, making it a severe threat to both personal and organizational data.

How To Fix

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

npm uninstall @voiceflow/eslint-config

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 measure, users can remove the @voiceflow/eslint-config package from their project until a secure version is confirmed. This can be done by executing: npm uninstall @voiceflow/eslint-config.

Conclusion

The @voiceflow/eslint-config package has been compromised by a malicious worm that poses serious security threats to users. It is essential to take immediate action by updating to the latest version or removing the package entirely. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for @voiceflow/eslint-config →

Share this vulnerability

FAQ

The malicious code is designed to steal sensitive tokens and credentials, potentially leading to unauthorized access to user accounts.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

If you have installed the affected version, it is crucial to uninstall it immediately and update to the latest patched version.

Yes, the worm has the potential to destroy the user's home directory, which can lead to significant data loss.

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

How To Fix

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

npm uninstall @voiceflow/eslint-config

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