Malicious code in tppywpullstr (PyPI)

tppywpullstr Updated 02 Oct 2025

Summary

26/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7493: Malicious code in tppywpullstr (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

tppywpullstr is a package available on PyPI that provides functionality for pulling data from webpages. It is commonly used in Python projects to scrape web content and extract information. Unfortunately, this package has been found to contain malicious code, which poses a significant security risk to any project that includes it.

Vulnerability Detail

The tppywpullstr package has been compromised by the EsqueleSquad group, who published nearly 6000 malicious PyPi and NPM packages. These packages execute spyware and information-stealing malware. The specific vulnerability in tppywpullstr allows the execution of arbitrary code, potentially leading to unauthorized access, data theft, and other malicious activities. The malicious code can be triggered when the package is imported and used in a Python project.

How To Fix

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

pip uninstall tppywpullstr

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, you can manually inspect the code of the tppywpullstr package and remove any suspicious or malicious code segments. However, this is not recommended as it can be time-consuming and error-prone. It is best to completely remove the package and find a secure replacement.

Conclusion

The tppywpullstr package on PyPI has been found to contain malicious code, posing a significant security risk to projects that include it. It is crucial to remove this package and replace it with a trusted alternative to ensure the security and integrity of your project. Regularly updating and auditing your project's dependencies is also essential to prevent similar vulnerabilities. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for tppywpullstr →

Share this vulnerability

FAQ

The malicious code in tppywpullstr can lead to unauthorized access, data theft, and other malicious activities. It is essential to remove this package from your project to ensure the security and integrity of your data.

You can use tools like Vulert (https://vulert.com) to check if your project is affected by this vulnerability. Vulert analyzes your Pipfile.lock and provides real-time alerts for open-source vulnerabilities.

The best mitigation for this vulnerability is to remove the tppywpullstr package from your project and replace it with a trusted alternative. Regularly updating and auditing your project's dependencies is also crucial to prevent similar vulnerabilities.

Yes, you can continue using other packages from PyPI. However, it is important to ensure that the packages you use are from trusted sources and regularly updated to avoid potential security risks.

For further support on vulnerability remediation and securing your project, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

How To Fix

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

pip uninstall tppywpullstr

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