Malicious Code Detected in comradefy Package - Security Alert

comradefy Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17463: Malicious code in comradefy (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The comradefy package is an npm library designed for facilitating collaborative functionalities in JavaScript applications. It provides various tools to enhance user interaction and teamwork within web 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 comradefy package stems from the inclusion of malicious code that can compromise the integrity and security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions affecting the application's performance and user data. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall comradefy

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 comradefy package altogether and look for alternative libraries that provide similar functionalities without the associated risks. Ensure to review the security status of any new packages before integrating them into your project.

Conclusion

The discovery of malicious code in the comradefy package highlights the importance of maintaining vigilance when using open-source libraries. Users are advised to remove the affected package and seek secure alternatives to protect their applications from potential threats.

See every vulnerability recorded for comradefy →

Share this vulnerability

FAQ

Comradefy is an npm package designed to enhance collaborative features in JavaScript applications.

The malicious code can lead to unauthorized access and data breaches, compromising application security.

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.

Remove the comradefy package and replace it with a secure alternative. Monitor for any updates or patches from the official repository.

Yes, there are several alternative libraries available that provide similar functionalities without the security risks. Always review their security status before use.

How To Fix

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

npm uninstall comradefy

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