Malicious Code Detected in doedroid Package - Security Alert

doedroid Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18587: Malicious code in doedroid (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 doedroid package is an npm library designed for [insert functionality here, e.g., data manipulation, web scraping, etc.]. It is utilized by developers for its [insert key attributes, e.g., ease of use, performance, etc.]. However, a recent discovery has revealed that this package contains malicious code, posing a significant risk to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the doedroid package, which was introduced in version 0. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The malicious nature of the code can affect any project that includes doedroid, making it imperative for developers to address this issue promptly.

How To Fix

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

npm uninstall doedroid

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, consider replacing doedroid with an alternative package that offers similar functionality without the security risks. Ensure to review the alternatives thoroughly before implementation.

Conclusion

The discovery of malicious code in the doedroid package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for doedroid →

Share this vulnerability

FAQ

doedroid is an npm package used for [insert functionality]. It is popular among developers for its [insert key attributes].

The malicious code was identified by security researchers from Amazon Inspector, who reported it as part of their ongoing efforts to monitor open-source vulnerabilities.

Using doedroid can expose your application to various security threats, including unauthorized access and data breaches due to the embedded malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert provides real-time alerts without requiring code access. Visit Vulert Scanner to check your application.

If you have used doedroid, it is crucial to remove it from your project immediately and consider using an alternative package. Regularly update your dependencies to ensure security.

How To Fix

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

npm uninstall doedroid

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