Malicious Code Detected in charmbox Package - Security Alert

charmbox Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16852: Malicious code in charmbox (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 charmbox package is an npm library designed for creating charming user interfaces with ease. It offers a variety of features that enhance user experience, including customizable components and seamless integration with other libraries. However, it has been found to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the charmbox package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall charmbox

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 charmbox package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall charmbox'. This will help prevent any potential exploitation of the malicious code.

Conclusion

The charmbox package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Users are strongly advised to update to a patched version or remove the package until a fix is available. Regular monitoring with tools like Vulert can help maintain application security.

See every vulnerability recorded for charmbox →

Share this vulnerability

FAQ

Charmbox is an npm library used for creating charming user interfaces with customizable components.

The vulnerability involves malicious code that can compromise application security and lead to unauthorized access.

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

As a temporary measure, consider uninstalling the charmbox package to prevent exploitation until a secure version is available.

The vulnerability was discovered by Amazon Inspector, a security tool that helps identify potential risks in software packages.

How To Fix

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

npm uninstall charmbox

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