Malicious Code Detected in earhorn Package - MAL-2025-19082

earhorn Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19082: Malicious code in earhorn (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 earhorn package is an npm library designed for audio manipulation and playback in web applications. It provides developers with tools to easily integrate sound features into their projects. However, the package has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the earhorn package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or disrupt normal application functionality. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall earhorn

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, users can avoid using the earhorn package and implement alternative libraries for audio manipulation. For example, consider using the 'howler.js' library, which can be installed via npm with the command: npm install howler.

Conclusion

The earhorn package has been identified to contain malicious code, posing serious security risks to applications that utilize it. Users are advised to remove the package and consider secure alternatives while monitoring for any updates or patches that may address this vulnerability.

See every vulnerability recorded for earhorn →

Share this vulnerability

FAQ

The earhorn package is an npm library used for audio manipulation and playback in web applications.

The malicious code can compromise application security, allowing unauthorized access to data or execution of harmful commands.

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

Remove the earhorn package from your project and consider using a secure alternative library for audio manipulation.

Currently, there is no patched version available. It is recommended to remove the package and use alternatives until a fix is released.

How To Fix

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

npm uninstall earhorn

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