Critical Malicious Code Vulnerability in eadlinks Package

eadlinks Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19057: Malicious code in eadlinks (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 eadlinks package is a Node.js library designed for managing and linking external resources within applications. It is commonly used for its simplicity and efficiency in handling links. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the eadlinks package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The vulnerability affects all versions starting from 0, making it imperative for users to take immediate action to mitigate the risks associated with this issue.

How To Fix

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

npm uninstall eadlinks

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, you can remove the eadlinks package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall eadlinks'. This will help mitigate the risk of exploitation while you await a patched version.

Conclusion

The eadlinks package has been identified to contain malicious code, posing serious security threats to applications. Users are advised to update the package as soon as a patched version is available or to uninstall it temporarily to protect their systems. Regular monitoring for vulnerabilities is essential for maintaining application security.

See every vulnerability recorded for eadlinks →

Share this vulnerability

FAQ

The eadlinks package is used for managing and linking external resources in Node.js applications.

The malicious code can compromise application security, leading to unauthorized access and potential data breaches.

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

As of now, a patched version has not been released. Users should monitor the official repository for updates.

If immediate updates are not possible, consider uninstalling the package as a temporary workaround to mitigate risks.

How To Fix

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

npm uninstall eadlinks

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