Critical Vulnerability in codesweat: Malicious Code Detected

codesweat Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17257: Malicious code in codesweat (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 'codesweat' package is an npm library designed for developers to enhance their applications with various functionalities. It is widely used in the JavaScript ecosystem for its ease of integration and utility features. However, recent findings have revealed that this package contains malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the 'codesweat' package stems from the inclusion of malicious code that can compromise the security of applications relying on it. This code can lead to unauthorized access, data breaches, or other harmful effects on the system. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall codesweat

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, you can avoid using the 'codesweat' package altogether and look for alternative libraries that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the 'codesweat' package highlights the importance of vigilance in managing dependencies in software development. Users are urged to take immediate action to mitigate risks by uninstalling the package and seeking alternatives.

See every vulnerability recorded for codesweat →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise the integrity of applications using the package.

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

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

You should immediately uninstall the package and review your application for any potential security breaches.

Yes, consider researching and using other npm packages that offer similar functionalities without the security risks associated with codesweat.

How To Fix

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

npm uninstall codesweat

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