Malicious Code Detected in droidfit Package - Security Alert

droidfit Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18819: Malicious code in droidfit (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 droidfit package is an npm library designed for fitness tracking and related functionalities. It allows developers to integrate fitness-related features into their applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the droidfit package originates from the inclusion of malicious code that can compromise user data and application integrity. This malicious code can lead to unauthorized access, data theft, and potential exploitation of the affected systems. The issue affects all versions of the package starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall droidfit

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 droidfit package and explore alternative libraries that provide similar functionalities without the associated risks. It is advisable to conduct a thorough review of any third-party packages before integrating them into your applications.

Conclusion

The discovery of malicious code in the droidfit package highlights the importance of maintaining security in software development. Users are urged to take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for droidfit →

Share this vulnerability

FAQ

droidfit is an npm package designed for fitness tracking and related functionalities in applications.

The malicious code found in droidfit can compromise user data and application integrity, potentially leading to unauthorized access and data theft.

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

You should remove the droidfit package from your project and replace it with a secure alternative. If a patched version is released, update the package using npm update droidfit.

Yes, there are several alternative packages available for fitness tracking. It is recommended to review and select a package that has a good security track record.

How To Fix

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

npm uninstall droidfit

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