Critical Malicious Code Vulnerability in boost-chii-new Package

boost-chii-new Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6404: Malicious code in boost-chii-new (npm). Affects boost-chii-new versions 1.0.1 – 1.1.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The boost-chii-new package is an npm library designed for various functionalities in JavaScript applications. It is commonly used for enhancing user interfaces and providing additional features to web applications. However, certain versions of this package have been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability identified as MAL-2025-6404 originates from malicious code embedded within specific versions of the boost-chii-new package. This code can lead to unauthorized access, data breaches, or even complete system compromise. The affected versions include 1.0.1, 1.1.1, and 1.1.2, which were flagged by ReversingLabs for containing harmful elements that could exploit users' systems.

How To Fix

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

npm uninstall boost-chii-new

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

If immediate updating is not possible, consider removing the package from your project or replacing it with a similar library that does not have known vulnerabilities. You can uninstall the package using the command: 'npm uninstall boost-chii-new'.

Conclusion

The boost-chii-new package has been identified to contain malicious code in certain versions, which poses a significant risk to applications using it. It is essential to update to a secure version or implement workarounds to mitigate potential threats.

See every vulnerability recorded for boost-chii-new →

Share this vulnerability

FAQ

The boost-chii-new package is an npm library used in JavaScript applications to enhance user interfaces and provide additional functionalities.

The affected versions are 1.0.1, 1.1.1, and 1.1.2.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Consider removing the package or replacing it with an alternative library until you can update to a secure version.

Detailed information about this vulnerability can be found on the ReversingLabs website and the GitHub repository for malicious packages.

How To Fix

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

npm uninstall boost-chii-new

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