Malicious Code Detected in cinclude Package - Security Alert

cinclude Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17033: Malicious code in cinclude (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cinclude package is an npm library designed for including C/C++ code within JavaScript applications. It allows developers to seamlessly integrate native code, enhancing performance and functionality. However, the package has recently been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the cinclude package stems from the presence of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall cinclude

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, you can remove the cinclude package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall cinclude'. This will help mitigate the risk while you await a fix.

Conclusion

The cinclude package has been found to contain malicious code, posing significant security risks to applications that utilize it. It is crucial for developers to update or remove the package to protect their applications from potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for cinclude →

Share this vulnerability

FAQ

The cinclude package is used to include C/C++ code in JavaScript applications, allowing for enhanced performance and functionality.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as part of their ongoing efforts to monitor open-source vulnerabilities.

Using the compromised cinclude package can lead to unauthorized access, data breaches, and other harmful actions that may compromise the integrity of your application.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

If you cannot update the package right away, consider removing it from your project as a temporary measure to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall cinclude

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