Critical Malicious Code Vulnerability in cdk-integ-tools Package

cdk-integ-tools Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16694: Malicious code in cdk-integ-tools (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cdk-integ-tools package is a tool designed for integration testing within the AWS Cloud Development Kit (CDK) ecosystem. It facilitates the testing of CDK applications by providing utilities that streamline the process. However, this package has been found to contain malicious code, posing a significant risk to users who rely on it for their development workflows.

Vulnerability Detail

The vulnerability in the cdk-integ-tools package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other malicious activities. 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 cdk-integ-tools

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, users are advised to remove the cdk-integ-tools package from their project until a secure version is released. This can be done using the command: 'npm uninstall cdk-integ-tools'.

Conclusion

The cdk-integ-tools package has been identified to contain malicious code, which poses a serious threat to users. It is crucial to take immediate action by updating or removing the package to safeguard your applications. Stay informed about updates and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for cdk-integ-tools →

Share this vulnerability

FAQ

cdk-integ-tools is a package used for integration testing in AWS CDK applications, providing utilities for easier testing.

The malicious code can lead to unauthorized access and potential data breaches, posing a significant security risk.

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

Currently, there is no patched version available. Users should monitor the package repository for updates.

If removal is not an option, ensure that you implement strict security measures and monitor your application closely until a fix is available.

How To Fix

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

npm uninstall cdk-integ-tools

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