Malicious Code Detected in ezmoodle Package - Security Alert

ezmoodle Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20117: Malicious code in ezmoodle (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 ezmoodle package is a Node.js library designed for enhancing Moodle functionalities. It provides various features that allow developers to integrate and extend Moodle's capabilities. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the ezmoodle package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in all versions starting from 0, making it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall ezmoodle

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 ezmoodle package from their project until a secure version is released. This can be done using the command: npm uninstall ezmoodle. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the ezmoodle package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are strongly advised to take immediate action to mitigate risks by updating or removing the affected package.

See every vulnerability recorded for ezmoodle →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and may lead to data breaches.

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

Consider removing the package from your project as a temporary workaround until a secure version is available.

Yes, explore other npm packages that provide similar functionalities without the security risks associated with ezmoodle.

Utilize tools like Vulert to monitor your package-lock.json for vulnerabilities and receive real-time alerts.

How To Fix

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

npm uninstall ezmoodle

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