Malicious Code Detected in capsidea Package - Security Alert

capsidea Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16518: Malicious code in capsidea (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 capsidea package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity is compromised due to the presence of malicious code. This vulnerability poses a significant risk to developers and users relying on this package for secure and efficient application development.

Vulnerability Detail

The capsidea package has been identified to contain malicious code that can potentially harm users and their applications. This vulnerability originated from the introduction of harmful scripts within the package, which can lead to unauthorized access, data breaches, or other malicious activities. Developers using this package may unknowingly expose their applications to security threats, making it crucial to address this issue promptly.

How To Fix

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

npm uninstall capsidea

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 capsidea package from your project until a secure version is confirmed. You can do this by executing the command: 'npm uninstall capsidea'. This will help mitigate the risk associated with the malicious code until a fix is available.

Conclusion

The discovery of malicious code in the capsidea package poses a serious threat to developers and users. It is essential to take immediate action by updating or removing the package to safeguard applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for capsidea →

Share this vulnerability

FAQ

Capsidea is an npm package used for specific functionalities in JavaScript applications, but it has been compromised with malicious code.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in your package-lock.json file. Visit Vulert Scanner to use the Vulert playground without signup.

If immediate updates are not possible, consider removing the capsidea package from your project as a temporary measure to reduce risk.

Using the compromised capsidea package can lead to unauthorized access, data breaches, and other malicious activities that can harm your application and its users.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software without needing to access the code or install anything.

How To Fix

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

npm uninstall capsidea

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