Malicious Code Detected in cftoxml Package - Security Alert

cftoxml Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16741: Malicious code in cftoxml (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 cftoxml package is an npm module designed to facilitate the conversion of CloudFormation templates into XML format. It is commonly used in cloud infrastructure management to streamline the deployment of resources. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the cftoxml package originates 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 harmful actions within the affected systems. The malicious nature of the code makes it imperative for users to take immediate action to safeguard their environments.

How To Fix

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

npm uninstall cftoxml

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 can remove the cftoxml package from their project until a secure version is confirmed. This can be done using the command: npm uninstall cftoxml. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code within the cftoxml package poses a serious threat to users. It is crucial to take immediate action by updating or removing the package to protect your applications. Utilizing tools like Vulert can help monitor and alert you to vulnerabilities in real-time, ensuring your software remains secure.

See every vulnerability recorded for cftoxml →

Share this vulnerability

FAQ

The cftoxml package is used for converting AWS CloudFormation templates into XML format, aiding in cloud resource management.

You can check if your application is affected by this vulnerability using Vulert. Simply upload your package-lock.json file at Vulert Scanner to monitor and receive alerts for open-source vulnerabilities.

Using the compromised cftoxml package can lead to unauthorized access, data breaches, and other harmful actions that can compromise your application's security.

Yes, users are advised to update the cftoxml package to a patched version to mitigate the risks associated with the malicious code.

If immediate updates are not possible, consider uninstalling the cftoxml package and using alternative solutions 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 cftoxml

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