Malicious Code Detected in Chestlink Package - Security Alert

chestlink Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16972: Malicious code in chestlink (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 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 Chestlink package is an npm library designed for various functionalities, potentially including data handling and manipulation. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it. Users of this package should be aware of its vulnerabilities and take immediate action to secure their applications.

Vulnerability Detail

The vulnerability in the Chestlink package originates from the inclusion of malicious code, which can lead to unauthorized access, data breaches, or other harmful actions within an application. This issue affects all versions of the package starting from its introduction, making it critical for developers to address it promptly.

How To Fix

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

npm uninstall chestlink

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, consider using alternative packages that provide similar functionalities without the associated risks. Always review the security history of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the Chestlink package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to secure their applications by removing the affected package and considering alternatives.

See every vulnerability recorded for chestlink →

Share this vulnerability

FAQ

Chestlink is an npm package used for various functionalities in JavaScript applications, but it has been compromised with malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Remove the Chestlink package immediately and consider using alternative packages. If a patched version is released, update to that version.

Using a package with malicious code can lead to unauthorized access, data breaches, and potential harm to your application and its users.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and always review the security history of packages before use.

How To Fix

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

npm uninstall chestlink

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