Malicious Code Detected in codder Package - Security Alert

codder Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17245: Malicious code in codder (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 codder package is an npm library designed for developers to facilitate coding tasks. It offers various functionalities that enhance productivity and streamline workflows. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their applications.

Vulnerability Detail

The vulnerability in the codder package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this package. This code may 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 users to take immediate action.

How To Fix

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

npm uninstall codder

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 measure, users can avoid using the codder package and seek alternative libraries that provide similar functionalities without the associated risks. Additionally, implementing security measures such as code reviews and dependency scanning can help mitigate potential threats.

Conclusion

The discovery of malicious code in the codder package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to secure their applications by removing the affected package and monitoring for updates or alternatives.

See every vulnerability recorded for codder →

Share this vulnerability

FAQ

The codder package is an npm library designed to assist developers with various coding tasks, enhancing productivity.

The malicious code in codder can lead to unauthorized access and potential data breaches within applications that use it.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Remove the codder package from your project and consider using a secure alternative. If a patched version is released, update to that version.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security updates for the packages you use.

How To Fix

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

npm uninstall codder

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