Malicious Code Detected in ecademy Package - Security Alert

ecademy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19110: Malicious code in ecademy (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 ecademy package is a Node.js library that provides various functionalities for educational applications. It is widely used in the npm ecosystem for its ease of integration and user-friendly features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the ecademy package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action to safeguard their applications.

How To Fix

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

npm uninstall ecademy

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, consider removing the ecademy package from your project until a secure version is released. You can do this by running the command: npm uninstall ecademy.

Conclusion

The discovery of malicious code in the ecademy package poses a significant threat to applications that utilize it. Users are urged to take immediate action by updating or removing the package to ensure the security of their applications. Regular monitoring for vulnerabilities is essential, and tools like Vulert can assist in this process.

See every vulnerability recorded for ecademy →

Share this vulnerability

FAQ

The ecademy package is a Node.js library designed for educational applications, providing various functionalities to enhance user experience.

The malicious code found in the ecademy package can lead to unauthorized access and potential data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring access to the code.

Currently, there is no patched version available. Users should monitor the package for updates and apply them as soon as they are released.

If you cannot update the package right away, consider removing it from your project as a temporary measure to protect your application.

How To Fix

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

npm uninstall ecademy

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