Malicious Code Exfiltration in codefrequencychecker Package

codefrequencychecker Updated 07 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-126: Malicious code in codefrequencychecker (PyPI). Affects codefrequencychecker versions 0.0.1 – 0.0.7. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The codefrequencychecker package, available on PyPI, is designed to analyze and report on code frequency metrics. However, it has been found to contain malicious code that compromises user data. This vulnerability allows attackers to exfiltrate sensitive information such as browser cookies and passwords, posing a significant risk to users' privacy and security.

Vulnerability Detail

The vulnerability originates from a malicious actor identified as kam193, who has embedded code within the codefrequencychecker package. This code is capable of exfiltrating browser data, including cookies and passwords, and establishes a Telegram bot for ongoing data exfiltration. The malicious intent is clear, as the package functions as an infostealer, utilizing a Telegram webhook to transmit the stolen data. Users who have installed affected versions of the package are at risk of having their sensitive information compromised.

How To Fix

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

pip uninstall codefrequencychecker

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 codefrequencychecker package until a secure version is available. Additionally, users should consider using a virtual environment to isolate their projects and minimize the risk of exposure to malicious packages.

Conclusion

The discovery of malicious code in the codefrequencychecker package highlights the importance of vigilance when using open-source software. Users should take immediate action to protect their data by uninstalling affected versions and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for codefrequencychecker →

Share this vulnerability

FAQ

Versions 0.0.1, 0.0.2, 0.0.3, 0.0.5, and 0.0.7 of the codefrequencychecker package are known to be affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed the affected package, you should uninstall it immediately and refrain from using it until a secure version is released.

The Telegram bot is used by the malicious code to send the exfiltrated data to the attacker, allowing for ongoing data theft.

To protect your sensitive information, regularly update your packages, use trusted sources, and consider employing tools like Vulert to monitor for vulnerabilities in your software.

How To Fix

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

pip uninstall codefrequencychecker

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