Malicious code in pywhool (PyPI)

pywhool Updated 02 Oct 2025

Summary

17/05/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8589: Malicious code in pywhool (PyPI). Affects pywhool versions 1.0.0. 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

Pywhool is a package available on PyPI that provides functionality for [insert functionality]. It is widely used by developers for [insert common use cases]. However, the package has been found to contain malicious code, which poses a significant security risk to any application that includes it.

Vulnerability Detail

The vulnerability in pywhool originates from a malicious package campaign targeting developers. The payload is hidden using steganography, making it difficult to detect. Once the package is installed, it exfiltrates host information, potentially compromising sensitive data. The campaign has been identified by Checkmarx, and the specific malicious package has the SHA256 hash of 54738d1aef580f087fec1311b411aa6ddd2d7affb4b44353dd7f3d6a569a0ed9. The campaign also includes various URLs and IP addresses that are used for exfiltration and communication with the attacker's infrastructure.

How To Fix

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

pip uninstall pywhool

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

There is no known workaround for this vulnerability. It is essential to take immediate action by removing the pywhool package and following the recommended steps to fix the issue.

Conclusion

The presence of malicious code in the pywhool package poses a significant security risk to applications that include it. It is crucial to take immediate action by removing the package and replacing it with a trusted alternative. Regularly reviewing and updating the packages used in your application is essential to ensure the security of your software. For further support and guidance on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for pywhool →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your Pipfile.lock, and Vulert will analyze it for any open-source vulnerabilities, including this one.

While specific exploits targeting this vulnerability have not been disclosed, it is crucial to address the issue promptly to prevent any potential compromise of sensitive data.

While PyPI is a widely used package repository, it is essential to exercise caution and review the packages you include in your application. Regularly checking for vulnerabilities and using tools like Vulert can help ensure the security of your software.

If you discover a malicious package in your application, it is recommended to remove it immediately and report the incident to the package repository or the relevant security authorities. Additionally, consider conducting a thorough security review of your application to identify any potential impact.

To prevent similar vulnerabilities, it is crucial to follow best practices for secure software development. This includes regularly updating and reviewing the packages used in your application, using reputable sources for package dependencies, and implementing security measures such as code reviews and vulnerability scanning.

How To Fix

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

pip uninstall pywhool

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