Malicious Code Vulnerability in essentialss Package

essentialss Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6415: Malicious code in essentialss (npm). Affects essentialss versions 1.0.3 – 1.0.6. 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 essentialss package is an npm library designed for various utility functions that streamline essential operations in JavaScript applications. It is widely used due to its simplicity and effectiveness. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability identified as MAL-2025-6415 originates from malicious code embedded within the essentialss package. This code can compromise the security of applications utilizing the affected versions (1.0.3, 1.0.4, 1.0.5, 1.0.6). The ramifications include unauthorized access to sensitive data, potential data breaches, and exploitation of the application environment. Users are strongly advised to take immediate action to mitigate these risks.

How To Fix

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

npm uninstall essentialss

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 remove the essentialss package from their project until a secure version is confirmed. This can be done using the command:

npm uninstall essentialss

Conclusion

The discovery of malicious code within the essentialss package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update their packages promptly and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for essentialss →

Share this vulnerability

FAQ

The affected versions are 1.0.3, 1.0.4, 1.0.5, and 1.0.6.

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

Using the affected versions may lead to unauthorized access to sensitive data and exploitation of your application, which can result in data breaches.

While a specific patched version is not mentioned, it is recommended to update to the latest version of the essentialss package.

If immediate updates are not possible, consider uninstalling the essentialss package 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 essentialss

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