Malicious Code Detected in elf-stats-flickering-lantern-502 Package

Summary

05/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192332: Malicious code in elf-stats-flickering-lantern-502 (npm). Affects elf-stats-flickering-lantern-502 versions 1.0.0. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The elf-stats-flickering-lantern-502 package is an npm library designed for specific functionalities within JavaScript applications. However, it has been identified to contain malicious code, posing significant risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the elf-stats-flickering-lantern-502 package. This code can execute harmful actions on the host system, potentially compromising sensitive data and application integrity. The malicious code was detected by Amazon Inspector, indicating a serious security threat that requires immediate attention.

How To Fix

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

npm uninstall elf-stats-flickering-lantern-502

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 can remove the elf-stats-flickering-lantern-502 package from your project by executing the following command: npm uninstall elf-stats-flickering-lantern-502. This will prevent the execution of any malicious code until a secure alternative is implemented.

Conclusion

The elf-stats-flickering-lantern-502 package has been found to contain malicious code, posing serious security risks to applications. It is crucial to remove the package and replace it with a secure alternative to protect your application from potential threats.

See every vulnerability recorded for elf-stats-flickering-lantern-502 →

Share this vulnerability

FAQ

It is an npm library used in JavaScript applications, but it has been found to contain malicious code.

The malicious code was identified by Amazon Inspector, a security assessment service.

The risks include unauthorized access, data breaches, and potential compromise of application integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, uninstall the package using 'npm uninstall elf-stats-flickering-lantern-502' to mitigate risks until a secure alternative is found.

How To Fix

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

npm uninstall elf-stats-flickering-lantern-502

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