Malicious code in toolpost (PyPI)

toolpost Updated 02 Oct 2025

Summary

23/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-6889: Malicious code in toolpost (PyPI). 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

Toolpost is a Python package available on PyPI that provides various tools and utilities for developers. It is commonly used in Python projects for tasks such as logging, debugging, and testing. Unfortunately, the package has been found to contain malicious code, which can lead to the execution of spyware and information-stealing malware.

Vulnerability Detail

The vulnerability in toolpost arises from the inclusion of malicious code in the package. This code was introduced in version 0 and has been identified by the Checkmarx security team. The malicious code can be triggered when using the affected version of toolpost, potentially compromising the security and privacy of the system. It is important to note that this vulnerability is not present in earlier versions of the package.

How To Fix

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

pip uninstall toolpost

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 workaround, users can consider removing the affected version of toolpost from their projects and replacing it with a safe alternative. It is important to carefully review the replacement package to ensure it meets the required functionality and security standards. Here is an example of how to remove the affected version of toolpost using pip:

pip uninstall toolpost==0

Conclusion

In conclusion, the toolpost package on PyPI has been found to contain malicious code that can lead to the execution of spyware and information-stealing malware. Users are advised to update to a safe version of the package, downgrade if necessary, and take appropriate actions to mitigate any potential damage. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for toolpost →

Share this vulnerability

FAQ

Toolpost is a Python package available on PyPI that provides various tools and utilities for developers. It is commonly used in Python projects for tasks such as logging, debugging, and testing.

The malicious code in toolpost can lead to the execution of spyware and information-stealing malware. This can compromise the security and privacy of the system, potentially resulting in unauthorized access to sensitive information.

The vulnerability is present in version 0 of toolpost. Earlier versions of the package are not affected.

To fix the vulnerability, it is recommended to update to a version of toolpost that is not affected by the malicious code. Downgrading to a previous version is advised. Additionally, scanning the system for signs of compromise and taking appropriate actions is important.

Yes, users can remove the affected version of toolpost from their projects and replace it with a safe alternative. Careful review of the replacement package is necessary.

How To Fix

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

pip uninstall toolpost

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