Malicious Code Detected in cc-double-1 Package - Security Alert

cc-double-1 Updated 03 Jan 2026

Summary

02/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-11: Malicious code in cc-double-1 (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 cc-double-1 package is an npm library that is utilized in various JavaScript applications for its specific functionalities. However, it has been identified to contain malicious code, posing a significant risk to applications that depend on it. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability in the cc-double-1 package stems from the presence of malicious code that was discovered by Amazon Inspector. This code can potentially compromise the security of applications using this package, allowing attackers to execute harmful actions. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall cc-double-1

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 cc-double-1 package from your project until a secure version is available. You can do this by running the command: npm uninstall cc-double-1. This will prevent any potential exploitation of the malicious code while you seek a safer alternative.

Conclusion

The detection of malicious code in the cc-double-1 package poses a serious security threat to applications that utilize it. Users are strongly advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for cc-double-1 →

Share this vulnerability

FAQ

cc-double-1 is an npm package used in JavaScript applications, but it has been found to contain malicious code.

The malicious code was identified by Amazon Inspector, which scans packages for security vulnerabilities.

Using cc-double-1 can lead to unauthorized access, data breaches, and other malicious activities due to the embedded harmful code.

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

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

How To Fix

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

npm uninstall cc-double-1

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