Critical Malicious Code Vulnerability in deeparrow Package

deeparrow Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18176: Malicious code in deeparrow (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The deeparrow package is a JavaScript library available on npm, designed to facilitate various functionalities in web applications. It is commonly used for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the deeparrow package stems from the presence of malicious code that can compromise the security of applications using it. This code could lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall deeparrow

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 avoid using the deeparrow package entirely and look for alternative libraries that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the deeparrow package highlights the importance of regularly auditing dependencies in software projects. Developers should take immediate action to remove the affected package and seek alternatives to safeguard their applications.

See every vulnerability recorded for deeparrow →

Share this vulnerability

FAQ

The deeparrow package is a JavaScript library used in web applications for various functionalities, but it has been found to contain malicious code.

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

If you are using deeparrow, it is recommended to remove the package immediately and look for secure alternatives.

As of now, there is no patched version available. It is crucial to monitor the package repository for any updates.

Using a package with malicious code can lead to unauthorized access, data breaches, and other harmful actions that compromise the security of your application.

How To Fix

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

npm uninstall deeparrow

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