Malicious Code Detected in Chessnut Package - Security Alert

chessnut Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16971: Malicious code in chessnut (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 chessnut package is an npm library designed for chess-related functionalities, allowing developers to integrate chess games and features into their applications. It is widely used in various projects due to its ease of use and comprehensive features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the chessnut package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access, data theft, or other harmful actions that can severely impact the integrity and confidentiality of user data. The issue affects all versions of the package starting from its introduction, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall chessnut

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 chessnut package from their projects until a secure version is released. This can be done using the command: 'npm uninstall chessnut'. Consider using alternative libraries that do not have known vulnerabilities in the meantime.

Conclusion

The discovery of malicious code in the chessnut package poses a serious threat to applications that utilize it. Users are urged to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help keep your applications secure by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for chessnut →

Share this vulnerability

FAQ

Chessnut is an npm package that provides functionalities for integrating chess games into applications.

The malicious code can potentially allow unauthorized access and data theft from applications using the chessnut package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

It is recommended to uninstall the chessnut package immediately and monitor for updates or patches from the maintainers.

Yes, consider exploring other chess libraries available on npm that do not have known vulnerabilities.

How To Fix

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

npm uninstall chessnut

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