Malicious code in tploadlgtb (PyPI)

tploadlgtb Updated 02 Oct 2025

Summary

25/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7229: Malicious code in tploadlgtb (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

tploadlgtb is a package available on PyPI that is used for [provide a brief description of the package's functionality and key attributes]. It is vulnerable to a malicious code injection that was introduced in version 0 and discovered by Checkmarx. This vulnerability allows attackers to execute spyware and information-stealing malware.

Vulnerability Detail

The malicious code injection in tploadlgtb was introduced in version 0 and was discovered by Checkmarx. The code allows attackers to execute spyware and information-stealing malware. This can lead to unauthorized access to sensitive information, compromise of user data, and potential harm to the affected system. The malicious code can be found in the package's source code and is triggered when the package is installed or executed.

How To Fix

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

pip uninstall tploadlgtb

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 crucial to update to a fixed version of tploadlgtb as soon as possible.

Conclusion

tploadlgtb is vulnerable to a malicious code injection that allows attackers to execute spyware and information-stealing malware. It is crucial to update to a fixed version of the package to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tploadlgtb →

Share this vulnerability

FAQ

tploadlgtb is a package available on PyPI that [provide a brief description of the package's functionality and key attributes].

The malicious code injection in tploadlgtb was discovered by Checkmarx during their security research and analysis of PyPI packages.

The potential consequences of this vulnerability include unauthorized access to sensitive information, compromise of user data, and potential harm to the affected system.

No, there is no known workaround for this vulnerability. It is crucial to update to a fixed version of tploadlgtb as soon as possible.

To update tploadlgtb to a fixed version, you can use the package manager for your Python environment (e.g., pip) and specify the version that is not affected by the malicious code injection.

How To Fix

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

pip uninstall tploadlgtb

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