Malicious Code Detected in ehouse Package - Security Alert

ehouse Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19262: Malicious code in ehouse (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 ehouse package is a Node.js library commonly used for various functionalities in web applications. It provides developers with tools to enhance their applications but has recently been flagged for containing malicious code. This vulnerability poses a significant risk to users who rely on this package for their projects, potentially leading to unauthorized access or data breaches.

Vulnerability Detail

The ehouse package has been identified to contain malicious code that can compromise the security of applications utilizing it. This vulnerability originated from the package's codebase, which was found to be intentionally designed to execute harmful actions. Users of the ehouse package may face severe ramifications, including data theft, unauthorized access to sensitive information, and potential exploitation of their systems. It is crucial for developers to be aware of this issue and take immediate action to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall ehouse

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 ehouse package from your project until a secure version is released. You can uninstall it using the following command: npm uninstall ehouse. This will prevent any potential exploitation while you await a fix.

Conclusion

The ehouse package has been flagged for containing malicious code, posing significant risks to applications that utilize it. Immediate action is required to update or remove the package to safeguard against potential exploitation. Utilizing tools like Vulert can help monitor your applications for vulnerabilities effectively.

See every vulnerability recorded for ehouse →

Share this vulnerability

FAQ

The ehouse package is a Node.js library used for various functionalities in web applications, providing tools for developers.

The malicious code in ehouse is designed to execute harmful actions that could compromise the security of applications using the package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities, to check if your application is affected. Visit Vulert Scanner to use the Vulert playground without signup.

If you cannot update the package right away, consider removing it from your project as a temporary measure to avoid potential risks.

More information about the ehouse vulnerability can be found in the official GitHub repository and security advisories related to the package.

How To Fix

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

npm uninstall ehouse

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