Critical Malicious Code Vulnerability in cahnrs Package

cahnrs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16431: Malicious code in cahnrs (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 cahnrs package is an npm library designed to facilitate the creation of charts and graphs in web applications. It provides a range of functionalities for data visualization, making it popular among developers. However, it has recently been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The cahnrs package has been found to contain malicious code that could compromise the security of applications using it. This vulnerability originated from the introduction of harmful scripts in version 0 and has the potential to lead to unauthorized access, data breaches, or other malicious activities. Developers using this package should be aware of the risks associated with its use and take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall cahnrs

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, you can avoid using the cahnrs package altogether and explore alternative libraries for data visualization, such as Chart.js or D3.js. This will help maintain the security of your application while a permanent fix is being implemented.

Conclusion

The discovery of malicious code in the cahnrs package poses a significant threat to applications that utilize it. Developers are urged to take immediate action by removing the package and seeking alternatives to ensure the security of their applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain a secure development environment.

See every vulnerability recorded for cahnrs →

Share this vulnerability

FAQ

The cahnrs package is an npm library used for creating charts and graphs in web applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

You should remove the cahnrs package from your project and consider using a secure alternative for data visualization.

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

How To Fix

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

npm uninstall cahnrs

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