Malicious Code Detected in chaunter Package - Security Alert

chaunter Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16867: Malicious code in chaunter (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 chaunter package is an npm library designed for creating and managing chat applications. It provides functionalities such as message handling, user management, and real-time communication features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the chaunter package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, facilitate data exfiltration, or enable remote code execution. The presence of such vulnerabilities can lead to severe ramifications, including data breaches and loss of user trust.

How To Fix

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

npm uninstall chaunter

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 removing the chaunter package from your project until a secure version is available. You can uninstall it using the command: 'npm uninstall chaunter'. This will help mitigate the risk until a fix is implemented.

Conclusion

The chaunter package has been identified to contain malicious code, posing significant security risks. It is crucial for developers to update to the latest patched version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for chaunter →

Share this vulnerability

FAQ

The chaunter package is an npm library used for building chat applications, offering features like message handling and user management.

The malicious code found in chaunter can potentially lead to unauthorized access and data breaches.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Yes, a patched version of chaunter is available. Update the package using 'npm update chaunter' to secure your application.

If immediate updates are not possible, consider uninstalling the chaunter package to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall chaunter

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