Malicious code in tpproofsplitint (PyPI)
Summary
MAL-2023-7416: Malicious code in tpproofsplitint (PyPI). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The tpproofsplitint package is an open-source Python package available on PyPI. It is used for splitting proof obligations in the context of theorem proving. The package provides functionality to split proof obligations into sub-obligations, allowing for easier management and analysis. However, the package has been found to contain malicious code, potentially compromising the security and integrity of systems that use it.
Vulnerability Detail
The tpproofsplitint package has been identified as part of a larger set of nearly 6000 malicious PyPi and NPM packages published by the EsqueleSquad group. These packages execute spyware and information-stealing malware. The specific vulnerability in tpproofsplitint allows an attacker to execute arbitrary code on systems that use the package. This can lead to unauthorized access, data theft, and other malicious activities. The malicious code is introduced in version 0 of the package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
pip uninstall tpproofsplitintIf 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 tpproofsplitint package and following the recommended steps to mitigate the risk.
Conclusion
The tpproofsplitint package has been found to contain malicious code as part of a larger set of malicious PyPi and NPM packages. This vulnerability allows attackers to execute arbitrary code on systems that use the package, potentially leading to unauthorized access and data theft. It is crucial to remove the package from your system and replace it with a trusted alternative. Additionally, ensure that all packages and dependencies in your project are obtained from reputable sources and regularly updated to mitigate similar security risks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tpproofsplitint →
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 file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
No, it is not recommended to use any version of tpproofsplitint due to the presence of malicious code. It is crucial to remove the package entirely from your system.
There have been reports of systems being compromised due to the use of malicious PyPi and NPM packages, including those published by the EsqueleSquad group. While specific instances of this vulnerability being exploited may not be publicly documented, it is essential to take immediate action to mitigate the risk.
If you find the tpproofsplitint package in your project's dependencies, it is recommended to remove it immediately. Replace it with a trusted alternative and ensure that all packages and dependencies in your project are obtained from reputable sources.
If you have discovered this vulnerability or have additional information related to it, please contact supplychainsecurity@checkmarx.com or visit https://bit.ly/checkmarx-malicious-packages to report it to the Checkmarx team.
