Malicious Code Detected in dd-transcode-ctrl Package - Security Alert

dd-transcode-ctrl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18113: Malicious code in dd-transcode-ctrl (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 dd-transcode-ctrl package is an npm module designed for transcoding media files. It offers functionalities that allow developers to manipulate audio and video formats seamlessly. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the dd-transcode-ctrl package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or system manipulation. The malicious nature of the code raises serious concerns about the integrity and safety of the software ecosystem.

How To Fix

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

npm uninstall dd-transcode-ctrl

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, you can remove the dd-transcode-ctrl package from your project until a secure version is released. Use the following command to uninstall the package: npm uninstall dd-transcode-ctrl.

Conclusion

The discovery of malicious code in the dd-transcode-ctrl package highlights the importance of vigilance in managing open-source dependencies. Developers are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for dd-transcode-ctrl →

Share this vulnerability

FAQ

dd-transcode-ctrl is an npm package used for transcoding audio and video files, allowing developers to manipulate media formats.

The malicious code was identified by security researchers from Amazon Inspector, who monitor open-source packages for vulnerabilities.

Using the compromised dd-transcode-ctrl package can lead to unauthorized access, data breaches, and potential system manipulation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If immediate updates are not possible, consider removing the package from your project as a temporary measure 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 dd-transcode-ctrl

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