Malicious Code Detected in codepipeline Package - Security Alert

codepipeline Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17255: Malicious code in codepipeline (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 codepipeline package is an npm library designed to facilitate the integration and automation of continuous delivery pipelines in software development. It provides developers with tools to streamline their deployment processes. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the codepipeline package, which was introduced in version 0. This malicious code can lead to unauthorized access, data breaches, or the execution of harmful operations within the affected applications. The implications of this vulnerability can be severe, affecting the integrity and confidentiality of user data.

How To Fix

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

npm uninstall codepipeline

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 codepipeline package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall codepipeline'. This will prevent any potential exploitation of the malicious code.

Conclusion

The discovery of malicious code in the codepipeline package highlights the importance of regularly monitoring and updating dependencies in software projects. By taking immediate action to update or remove the affected package, developers can safeguard their applications against potential threats.

See every vulnerability recorded for codepipeline →

Share this vulnerability

FAQ

The codepipeline package is an npm library used for automating continuous delivery pipelines in software development.

The malicious code can lead to unauthorized access and potential data breaches within applications using the codepipeline package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, you should check for a patched version of the codepipeline package and update it to mitigate the vulnerability.

As a temporary measure, consider uninstalling the codepipeline package to prevent any exploitation of the malicious code.

How To Fix

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

npm uninstall codepipeline

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