Malicious Code Detected in com.unity.recorder Package

com.unity.recorder Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17360: Malicious code in com.unity.recorder (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The com.unity.recorder package is an npm library designed for recording gameplay and other interactive experiences within the Unity game engine. It provides developers with tools to capture video and audio, making it easier to create tutorials, demos, and other media content. However, this package has been found to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the com.unity.recorder package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. 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 com.unity.recorder

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 measure, users can remove the com.unity.recorder package from their project until a secure version is released. This can be done by executing the following command: npm uninstall com.unity.recorder. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the com.unity.recorder package highlights the importance of maintaining vigilance regarding open-source dependencies. Users are encouraged to update their packages regularly and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for com.unity.recorder →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to user data and system resources, posing a significant security threat.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

If an immediate update is not possible, consider uninstalling the package and using alternative solutions until a secure version is available.

Regularly check the package repository and subscribe to security alerts for the packages you use to stay updated on any vulnerabilities.

Yes, tools like Vulert can automate the monitoring of your package-lock.json file to alert you of any vulnerabilities in real-time.

How To Fix

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

npm uninstall com.unity.recorder

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