Malicious Code Detected in cm-api Package - Security Alert

cm-api Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17210: Malicious code in cm-api (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 cm-api package is a Node.js library designed for managing and interacting with various APIs. It provides developers with tools to streamline API calls and enhance application functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The cm-api package has been identified to contain malicious code that can compromise the security of applications using it. This vulnerability originated from the package itself, which was found to have been tampered with, potentially allowing unauthorized access to sensitive data or enabling malicious activities within the application environment. The ramifications of this vulnerability can include data breaches, unauthorized API access, and overall application instability.

How To Fix

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

npm uninstall cm-api

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 feasible, consider removing the cm-api package from your project until a secure version is available. You can do this by running: npm uninstall cm-api. Additionally, review your codebase for any dependencies that may rely on cm-api and assess alternative packages that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the cm-api package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Developers should take immediate action to mitigate risks by updating or removing the affected package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for cm-api →

Share this vulnerability

FAQ

cm-api is a Node.js library used for managing and interacting with APIs, providing tools for developers to enhance their applications.

The malicious code was identified through security audits and reports from security tools, including findings from Amazon Inspector.

Using the compromised cm-api package can lead to data breaches, unauthorized access to APIs, and potential exploitation of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall cm-api

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