Malicious Code Detected in jslint-config Package: Version 10.22.2

jslint-config Updated 28 Feb 2026

Summary

26/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1055: Malicious code in jslint-config (npm). Affects jslint-config versions 10.22.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The jslint-config package is a configuration tool for JSLint, a JavaScript code quality tool that helps developers identify potential issues in their code. This package is commonly used in JavaScript projects to enforce coding standards and improve code quality. However, the specific version 10.22.2 has been identified as malicious, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in jslint-config arises from its malicious behavior, which includes communicating with a domain linked to harmful activities and executing commands that can compromise system integrity. This behavior can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The origin of this vulnerability has been traced back to the OpenSSF Package Analysis project, which flagged this version as malicious due to its suspicious activities.

How To Fix

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

npm uninstall jslint-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 workaround, you can remove the jslint-config package from your project until a secure version is confirmed. Use the following command to uninstall the package: npm uninstall jslint-config.

Conclusion

The jslint-config package version 10.22.2 has been identified as malicious, posing significant risks to users. It is crucial to update or remove the package to protect your applications from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for jslint-config →

Share this vulnerability

FAQ

jslint-config is a configuration package for JSLint, which helps enforce coding standards in JavaScript projects.

This version has been flagged for communicating with a malicious domain and executing harmful commands.

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.

As a temporary measure, you can uninstall the jslint-config package to mitigate risks until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert for vulnerabilities in open-source software, providing real-time insights.

How To Fix

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

npm uninstall jslint-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