Malicious Code Detected in elderberry-cherry-doee Package

elderberry-cherry-doee Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19329: Malicious code in elderberry-cherry-doee (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-cherry-doee package is an npm library designed for specific functionalities within JavaScript applications. It is often utilized for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the elderberry-cherry-doee package stems from the inclusion of malicious code, which can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall elderberry-cherry-doee

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 measure, consider replacing the elderberry-cherry-doee package with an alternative library that provides similar functionality without the associated risks. Always ensure to review the security of any new packages before integration.

Conclusion

The discovery of malicious code in the elderberry-cherry-doee package underscores the importance of vigilance when using third-party libraries. By promptly addressing this vulnerability, developers can protect their applications from potential threats.

See every vulnerability recorded for elderberry-cherry-doee →

Share this vulnerability

FAQ

The elderberry-cherry-doee package is an npm library used in JavaScript applications, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.

You should uninstall the elderberry-cherry-doee package immediately and consider using an alternative library.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Using this package can lead to unauthorized access, data breaches, and other harmful actions within your application.

How To Fix

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

npm uninstall elderberry-cherry-doee

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