Critical Malicious Code Vulnerability in optimizer-cpu Package

optimizer-cpu Updated 06 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-765: Malicious code in optimizer-cpu (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The optimizer-cpu package is a Node.js library commonly used in JavaScript applications for optimizing CPU usage. It is designed to enhance performance by managing computational tasks efficiently. However, this package has been found to contain malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the optimizer-cpu package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. Systems running this package should be considered fully compromised, and immediate action is required to mitigate potential damage.

How To Fix

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

npm uninstall optimizer-cpu

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 workaround, ensure that the optimizer-cpu package is uninstalled using the command: npm uninstall optimizer-cpu. Additionally, monitor your system for any unusual activity and consider using security tools to scan for remaining threats.

Conclusion

The optimizer-cpu package contains malicious code that poses a serious security threat. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for optimizer-cpu →

Share this vulnerability

FAQ

The optimizer-cpu package is a Node.js library designed to optimize CPU usage in JavaScript applications, enhancing performance and efficiency.

The malicious code can compromise your entire system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

Immediately uninstall the optimizer-cpu package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts for any issues.

How To Fix

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

npm uninstall optimizer-cpu

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