Critical Malicious Code Vulnerability in @cpce/console-sub-app

@cpce/console-sub-app Updated 02 Oct 2025

Summary

15/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5866: Malicious code in @cpce/console-sub-app (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 @cpce/console-sub-app package is an npm library designed for building console-based sub-applications. It provides developers with tools to create modular applications that can be integrated into larger systems. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @cpce/console-sub-app package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications are severe, as attackers may gain complete control over the affected system, leading to potential data breaches and loss of integrity.

How To Fix

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

npm uninstall @cpce/console-sub-app

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

Currently, the only effective workaround is to uninstall the @cpce/console-sub-app package. You can do this by running the following command in your terminal: npm uninstall @cpce/console-sub-app. Additionally, rotate all secrets and keys stored on the affected system from a secure, unaffected machine.

Conclusion

The @cpce/console-sub-app package contains critical malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and monitor for updates regarding a patched version.

See every vulnerability recorded for @cpce/console-sub-app →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

As of now, there is no patched version available. It is crucial to uninstall the package until further notice.

Failure to address this vulnerability can lead to complete system compromise, data breaches, and unauthorized access to sensitive information.

It is not recommended to reinstall the package until a secure version is released. Monitor the package repository for updates.

How To Fix

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

npm uninstall @cpce/console-sub-app

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