Malicious Code Detected in cpaas-common Package - Security Alert

cpaas-common Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17646: Malicious code in cpaas-common (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 cpaas-common package is an npm library commonly used for various functionalities in JavaScript applications. It is designed to facilitate communication and integration with cloud-based services. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cpaas-common package. This code can potentially compromise the integrity of applications, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from version 0, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall cpaas-common

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 cpaas-common package from your project until a secure version is released. You can do this by executing the following command: npm uninstall cpaas-common. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the cpaas-common package poses a serious threat to applications utilizing this library. Users are urged to take immediate action by updating or removing the package to safeguard their systems. Continuous monitoring and awareness of updates are essential for maintaining security.

See every vulnerability recorded for cpaas-common →

Share this vulnerability

FAQ

cpaas-common is an npm library used for integrating cloud-based services in JavaScript applications.

The exact nature of the malicious code has not been disclosed, but it poses significant security risks, including unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

Currently, there is no patched version available. Users should monitor the package repository for updates and apply them as soon as they are released.

If removal is not feasible, consider implementing additional security measures, such as code reviews and monitoring for unusual activity, until a secure version is released.

How To Fix

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

npm uninstall cpaas-common

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