Critical Malicious Code Vulnerability in ejrfsqmkdconukbl Package

ejrfsqmkdconukbl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19277: Malicious code in ejrfsqmkdconukbl (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 ejrfsqmkdconukbl package is an npm library used for various functionalities in JavaScript applications. It is designed to facilitate certain tasks within the ecosystem, but it has been identified as containing malicious code that poses a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the ejrfsqmkdconukbl package stems from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue originated from the package's initial release, and it affects all versions starting from 0.

How To Fix

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

npm uninstall ejrfsqmkdconukbl

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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security of third-party packages before integrating them into your application.

Conclusion

The ejrfsqmkdconukbl package has been identified as containing malicious code, posing a serious security threat. Users are advised to uninstall the package and seek alternatives to protect their applications. Regular monitoring and auditing of dependencies are essential to maintain security.

See every vulnerability recorded for ejrfsqmkdconukbl →

Share this vulnerability

FAQ

ejrfsqmkdconukbl is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you are using the ejrfsqmkdconukbl package, you should uninstall it immediately and look for alternative packages.

Currently, there is no patched version available for the ejrfsqmkdconukbl package. Users should uninstall the package to mitigate risks.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.

How To Fix

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

npm uninstall ejrfsqmkdconukbl

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