Malicious Code Detected in npm Package 'ejercico'

ejercico Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19276: Malicious code in ejercico (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 'ejercico' package is an npm library designed for educational purposes, often used in coding exercises and tutorials. It provides various functionalities to assist developers in learning JavaScript and related technologies. However, it has been identified to contain malicious code, posing significant risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the 'ejercico' package arises from the presence of malicious code that can compromise the security of applications utilizing this package. 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 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 ejercico

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, users can isolate the functionality that relies on the 'ejercico' package and replace it with custom implementations or alternative libraries that do not pose security risks.

Conclusion

The 'ejercico' package has been identified as containing malicious code, posing significant risks to users. Immediate action is required to remove the package and replace it with secure alternatives. Users are encouraged to utilize tools like Vulert to monitor their applications for vulnerabilities.

See every vulnerability recorded for ejercico →

Share this vulnerability

FAQ

The 'ejercico' package is an npm library used for educational purposes, particularly in coding exercises and tutorials.

The malicious code in 'ejercico' can lead to unauthorized access and potential data breaches in applications that use it.

You can use Vulert, a tool that monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should remove the 'ejercico' package from your project and replace it with a secure alternative immediately.

Currently, there is no patched version available. It is recommended to avoid using the package until further notice.

How To Fix

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

npm uninstall ejercico

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