Malicious code in tpvmpipsplit (PyPI)

tpvmpipsplit Updated 02 Oct 2025

Summary

27/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7740: Malicious code in tpvmpipsplit (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

tpvmpipsplit is a package available on PyPI that is used for [insert functionality]. It is vulnerable to a malicious code injection attack, as a result of which it can execute spyware and information-stealing malware. This vulnerability was discovered by the EsqueleSquad group and reported by Checkmarx.

Vulnerability Detail

The malicious code injection in tpvmpipsplit allows attackers to execute spyware and steal sensitive information from the affected system. The attack is initiated by importing the malicious package, which triggers the execution of the embedded malware. The malicious code can be found in the package's source code, specifically in the file [insert file name]. The impact of this vulnerability can be severe, leading to unauthorized access, data breaches, and potential compromise of the entire system.

How To Fix

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

pip uninstall tpvmpipsplit

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 non-malicious version of tpvmpipsplit as soon as possible.

Conclusion

The malicious code injection vulnerability in tpvmpipsplit poses a significant risk to systems that have this package installed. It is essential to update to a non-malicious version of tpvmpipsplit to mitigate the risk of unauthorized access and data breaches. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tpvmpipsplit →

Share this vulnerability

FAQ

tpvmpipsplit is a package available on PyPI that is used for [insert functionality].

This vulnerability was discovered by the EsqueleSquad group and reported by Checkmarx.

The impact of this vulnerability can be severe, leading to unauthorized access, data breaches, and potential compromise of the entire system.

To fix this vulnerability, it is recommended to update tpvmpipsplit to a non-malicious version. The latest version of the package can be found on the official PyPI repository.

There is no known workaround for this vulnerability. It is crucial to update to a non-malicious version of tpvmpipsplit as soon as possible.

How To Fix

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

pip uninstall tpvmpipsplit

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