Malicious Code Detected in elderberry-686-project: A Critical npm Vulnerability

elderberry-686-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19319: Malicious code in elderberry-686-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The elderberry-686-project is an npm package designed for developers to streamline specific functionalities within their applications. However, it has been identified as containing malicious code, which poses significant security risks to users and their projects. This vulnerability can compromise the integrity of applications that rely on this package, making it crucial for developers to be aware of its implications.

Vulnerability Detail

The vulnerability in the elderberry-686-project stems from the inclusion of malicious code within the package. This code can potentially allow unauthorized access to sensitive data, execute harmful commands, or disrupt normal operations of applications utilizing this package. The malicious nature of the code was confirmed through security assessments, highlighting the need for immediate action to mitigate risks associated with its use.

How To Fix

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

npm uninstall elderberry-686-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 measure, consider replacing the elderberry-686-project with an alternative package that offers similar functionalities without the associated risks. Additionally, you can implement security measures such as code reviews and dependency audits to identify and mitigate potential threats.

Conclusion

The discovery of malicious code in the elderberry-686-project poses a serious threat to developers and their applications. Immediate action is required to remove the package and seek alternatives or updates. Staying informed about vulnerabilities is crucial for maintaining secure software.

See every vulnerability recorded for elderberry-686-project →

Share this vulnerability

FAQ

The elderberry-686-project is an npm package used by developers for specific functionalities within their applications.

The malicious code can potentially allow unauthorized access to sensitive data and disrupt application operations.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Remove the elderberry-686-project package from your project and look for a secure alternative or a patched version.

Regularly check the package's repository for updates and utilize tools like Vulert to monitor your dependencies.

How To Fix

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

npm uninstall elderberry-686-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