Critical Malicious Code Vulnerability in smm-youtube Package

smm-youtube Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192639: Malicious code in smm-youtube (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The smm-youtube package is an npm library designed for interacting with YouTube services, allowing developers to integrate various YouTube functionalities into their applications. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the smm-youtube package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, and it is classified under CWE-506, indicating the presence of harmful code within the software.

How To Fix

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

npm uninstall smm-youtube

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

There are no effective workarounds for this vulnerability other than complete removal of the smm-youtube package. Users should ensure that they do not run any applications that depend on this package until it has been removed.

Conclusion

The smm-youtube package contains malicious code that poses a serious security threat. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for smm-youtube →

Share this vulnerability

FAQ

You should uninstall the smm-youtube package immediately and rotate any sensitive information stored on the affected machine.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

No, there is currently no patched version available for the smm-youtube package.

Failure to remove the package can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your computer.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and ensure that you only use trusted packages from reputable sources.

How To Fix

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

npm uninstall smm-youtube

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