Malicious Code Detected in everglow-moose-eaf816-project: A Critical Security Concern

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19956: Malicious code in everglow-moose-eaf816-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 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 package 'everglow-moose-eaf816-project' is an npm package that serves a specific functionality within the JavaScript ecosystem. It is designed to facilitate certain operations in web development. However, it has been identified to contain malicious code, which poses a significant risk to users and their applications. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability in 'everglow-moose-eaf816-project' originates from the inclusion of malicious code within the package. This code can execute harmful actions without the user's consent, potentially compromising sensitive information or system integrity. The ramifications of this vulnerability are severe, as it can affect any application that relies on this package, leading to widespread security issues.

How To Fix

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

npm uninstall everglow-moose-eaf816-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, you may consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The discovery of malicious code in the 'everglow-moose-eaf816-project' npm package highlights the importance of vigilance in managing open-source dependencies. Users are advised to take immediate action to mitigate risks associated with this vulnerability by removing the affected package and monitoring their applications for any unusual behavior.

See every vulnerability recorded for everglow-moose-eaf816-project →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromise.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

Regularly updating your dependencies and using tools like Vulert can help monitor and alert you to potential vulnerabilities.

Consider using alternative packages and ensure to monitor your application closely for any suspicious activity.

Detailed information can be found on the GitHub repository linked in the vulnerability report.

How To Fix

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

npm uninstall everglow-moose-eaf816-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