Malicious Code Detected in eslint-config-sdk Package - Version 101.0.1

eslint-config-sdk Updated 27 Dec 2025

Summary

27/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192952: Malicious code in eslint-config-sdk (npm). Affects eslint-config-sdk versions 101.0.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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

eslint-config-sdk is a configuration package for ESLint, a popular JavaScript linting utility that helps developers identify and fix problems in their JavaScript code. This package is designed to provide a set of predefined rules and settings that can be easily shared across projects. However, the specific version 101.0.1 has been flagged for containing malicious code, which poses a significant risk to users who rely on it for maintaining code quality.

Vulnerability Detail

The vulnerability in eslint-config-sdk arises from its communication with a domain associated with malicious activity. This behavior can lead to unauthorized data access, potential data breaches, and compromise of the development environment. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which flagged version 101.0.1 as harmful, indicating that users should exercise caution when using this version.

How To Fix

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

npm uninstall eslint-config-sdk

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 remove the eslint-config-sdk package from your project by executing 'npm uninstall eslint-config-sdk'. This will prevent any potential malicious activity while you seek an alternative solution or wait for a patched version.

Conclusion

The eslint-config-sdk package version 101.0.1 has been identified as malicious, posing significant risks to users. It is crucial to update to the latest version or remove the package to protect your development environment. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for eslint-config-sdk →

Share this vulnerability

FAQ

eslint-config-sdk is a configuration package for ESLint that provides a set of rules and settings for JavaScript linting.

The malicious nature of eslint-config-sdk was identified by the OpenSSF Package Analysis project, which monitors packages for security vulnerabilities.

Using the affected version (101.0.1) can lead to unauthorized data access, potential data breaches, and compromise of your development environment.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package immediately, consider uninstalling it as a temporary measure to mitigate risks until you can apply a fix.

How To Fix

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

npm uninstall eslint-config-sdk

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