Malicious Code Detected in cinelerra Package - Security Alert

cinelerra Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17041: Malicious code in cinelerra (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 cinelerra package is a multimedia application designed for video editing and production. It offers a range of features for both amateur and professional users, including advanced editing tools, support for various video formats, and a user-friendly interface. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability in the cinelerra package stems from the inclusion of malicious code that can compromise user systems. This code may allow unauthorized access, data theft, or other harmful actions. The issue originated from the package's source code and affects all versions starting from its introduction. Users of the cinelerra package are at risk of exploitation if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall cinelerra

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 cinelerra package from their projects until a secure version is confirmed. This can be done using the command: npm uninstall cinelerra. Consider using alternative packages for multimedia editing in the meantime.

Conclusion

The discovery of malicious code in the cinelerra package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to update or remove the affected package to safeguard their systems.

See every vulnerability recorded for cinelerra →

Share this vulnerability

FAQ

Cinelerra is a multimedia application used for video editing and production, offering various tools for users.

The malicious code can potentially allow unauthorized access and data theft from user systems.

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, uninstall the cinelerra package using 'npm uninstall cinelerra' and consider using alternative solutions.

Yes, Vulert allows you to monitor open-source vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

npm uninstall cinelerra

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