Malicious Code Detected in ejson2env Package - Security Alert

ejson2env Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19280: Malicious code in ejson2env (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ejson2env package is an npm library designed to facilitate the conversion of environment variables from JSON format. It is commonly used in Node.js applications for managing configuration settings. However, the package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the ejson2env package arises from the presence of malicious code that can compromise the security of applications using this library. This code could potentially lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall ejson2env

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 ejson2env package from your project until a secure version is released. You can do this by executing the following command: npm uninstall ejson2env. Additionally, review your codebase for any dependencies that may rely on this package and assess their security.

Conclusion

The discovery of malicious code in the ejson2env package poses a serious threat to applications that utilize this library. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure ongoing security.

See every vulnerability recorded for ejson2env →

Share this vulnerability

FAQ

The ejson2env package is used to convert environment variables from JSON format, making it easier to manage configuration settings in Node.js applications.

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 any signup.

If you cannot update the package right away, consider removing it from your project as a temporary measure and look for alternative solutions that do not pose security risks.

While specific exploits have not been publicly disclosed, the presence of malicious code indicates a high risk of potential exploitation, which could lead to unauthorized access or data breaches.

You can stay informed by following the package repository on GitHub or subscribing to security alerts related to npm packages.

How To Fix

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

npm uninstall ejson2env

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