Malicious Code Execution Vulnerability in c2-client Package

c2-client Updated 24 Sep 2026

Summary

24/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17165: Malicious code in c2-client (npm). Affects c2-client versions 1.0.0. 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 c2-client package is an npm module designed for command and control (C2) operations. It is intended for use in environments where automated control of systems is necessary. However, this package has been identified as containing malicious code that can execute unauthorized commands on the installer's machine during installation, posing significant security risks.

Vulnerability Detail

The vulnerability originates from a postinstall hook defined in the package.json file of the c2-client package. This hook executes a setup script (setup.js) automatically when the package is installed. The script runs with the privileges of the user installing the package and has access to the network, allowing it to potentially establish a command channel controlled by an attacker or execute arbitrary code. This behavior is classified under CWE-506, indicating the presence of embedded malicious code.

How To Fix

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

npm uninstall c2-client

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, avoid installing the c2-client package altogether. If it is already installed, you can remove it using the command: npm uninstall c2-client. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities.

Conclusion

The c2-client package has been identified as containing malicious code that can execute unauthorized commands during installation. It is essential to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for c2-client →

Share this vulnerability

FAQ

The c2-client package is an npm module designed for command and control operations, allowing automated management of systems.

The vulnerability manifests through a postinstall hook that executes a setup script, which can run malicious code with the installer's privileges.

The risks include unauthorized code execution, potential data breaches, and the establishment of a command channel controlled by an attacker.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you have installed the c2-client package, you should uninstall it immediately using the command: npm uninstall c2-client.

How To Fix

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

npm uninstall c2-client

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