Critical Malicious Code Vulnerability in my-js-cdn Package

my-js-cdn Updated 02 Oct 2025

Summary

08/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5710: Malicious code in my-js-cdn (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 my-js-cdn package is an npm library designed for delivering JavaScript content via a content delivery network (CDN). It is used by developers to efficiently load scripts in web applications. However, this package has been identified to contain embedded malicious code, making it a significant security risk for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the my-js-cdn package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall my-js-cdn

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

Currently, the only effective workaround is to uninstall the my-js-cdn package. You can do this by running the following command in your terminal: npm uninstall my-js-cdn. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The my-js-cdn package has been identified as containing malicious code, posing a severe risk to any systems that have it installed. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for my-js-cdn →

Share this vulnerability

FAQ

You should uninstall the my-js-cdn package immediately and rotate any sensitive information stored on the affected system.

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 requiring any signup.

As of now, there is no patched version available. The best course of action is to remove the package entirely.

Failing to remove the package can lead to unauthorized access to your system, potentially compromising sensitive data and allowing attackers to execute malicious actions.

It is advisable to review the security history of other packages from the same author before using them, as they may also contain vulnerabilities.

How To Fix

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

npm uninstall my-js-cdn

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