Malicious Code Detected in elderberry-hd7-project: A Critical Security Alert

elderberry-hd7-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19339: Malicious code in elderberry-hd7-project (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The elderberry-hd7-project is an npm package designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and feature set. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the elderberry-hd7-project arises from the inclusion of malicious code within the package. This code can lead to unauthorized access, data breaches, or other forms of exploitation. The issue was identified in version 0 and has been documented as MAL-2025-19339. The ramifications of this vulnerability can be severe, potentially compromising the integrity and security of applications using this package.

How To Fix

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

npm uninstall elderberry-hd7-project

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 elderberry-hd7-project package from your project until a secure version is released. You can do this by executing: npm uninstall elderberry-hd7-project.

Conclusion

The discovery of malicious code in the elderberry-hd7-project package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for elderberry-hd7-project →

Share this vulnerability

FAQ

The elderberry-hd7-project is an npm package used in JavaScript applications for various functionalities.

The malicious code was identified through security assessments conducted by Amazon Inspector.

The risks include unauthorized access to sensitive data, potential data breaches, and exploitation of the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.

How To Fix

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

npm uninstall elderberry-hd7-project

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