Malicious code in tpproofpinglib (PyPI)

tpproofpinglib Updated 02 Oct 2025

Summary

27/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7408: Malicious code in tpproofpinglib (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

tpproofpinglib is a package available on PyPI that provides functionality for proof of ping. It is commonly used in Python projects to verify network connectivity and measure latency. The package allows developers to perform ping operations and retrieve ping statistics. However, the package has been found to contain malicious code, which poses a security risk to applications that utilize it.

Vulnerability Detail

The tpproofpinglib 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 tpproofpinglib allows the execution of arbitrary code, potentially leading to unauthorized access, data theft, or other malicious activities. The malicious code can be triggered when using the affected package, putting applications and their users at risk.

How To Fix

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

pip uninstall tpproofpinglib

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 remove the affected package and replace it with a secure alternative.

Conclusion

The tpproofpinglib package on PyPI has been found to contain malicious code, posing a significant security risk to applications that use it. It is crucial to remove the affected package and replace it with a trusted alternative. Regularly monitoring and updating the packages used in your project is essential to mitigate the risk of known vulnerabilities. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for tpproofpinglib →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary code on your application, potentially leading to unauthorized access, data theft, or other malicious activities.

You can use the Vulert playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply provide your Pipfile.lock, and Vulert will analyze it for open-source vulnerabilities.

While there may not be specific instances of this vulnerability being exploited in the wild, the presence of malicious code in the tpproofpinglib package poses a significant risk to applications that use it.

While PyPI is a widely used package repository, it is essential to exercise caution and review the packages you include in your project. Regularly update and review the packages to ensure they are from trusted sources and free from known vulnerabilities.

If you discover a vulnerability in an open-source package, it is recommended to report it to the package maintainer or the relevant security team. They can then take appropriate actions to address the vulnerability and release a patched version.

How To Fix

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

pip uninstall tpproofpinglib

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