Malicious code in tpstrpycv (PyPI)
Summary
MAL-2023-7628: Malicious code in tpstrpycv (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
tpstrpycv is a package available on PyPI that provides functionality for [insert functionality]. It is widely used in [mention relevant industries or projects]. The package 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 Checkmarx security team.
Vulnerability Detail
The vulnerability (MAL-2023-7628) in tpstrpycv originates from a malicious package published on PyPI by the EsqueleSquad group. The package contains code that can download and execute spyware and information-stealing malware on the user's system. This can lead to unauthorized access to sensitive information, compromise of user privacy, and potential damage to systems. The malicious code can be triggered when the vulnerable package is installed or used in a project.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
pip uninstall tpstrpycvIf 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 specific workaround for this vulnerability. The best course of action is to follow the steps mentioned in the 'how_to_fix' section and remove the vulnerable package from your project.
Conclusion
The tpstrpycv package on PyPI has been found to contain malicious code that can execute spyware and information-stealing malware. It is crucial to remove this package from your project and replace it with a trusted alternative. Regularly updating and reviewing the packages used in your project, as well as running security scans, are important measures to ensure the integrity and security of your software. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for tpstrpycv →
FAQ
You can use tools like Vulert (https://vulert.com) to scan your project's Pipfile.lock and identify if the tpstrpycv package is present and vulnerable.
The consequences of this vulnerability include unauthorized access to sensitive information, compromise of user privacy, and potential damage to systems. It is important to take immediate action to mitigate the risk.
At the time of discovery, there were no known exploits of this vulnerability. However, it is always recommended to address vulnerabilities promptly to minimize the risk of exploitation.
The Checkmarx security team has reported this vulnerability and is actively working with the PyPI community to address the issue. It is recommended to stay updated with security advisories and follow the recommended steps to fix the vulnerability as soon as possible.
If you come across any suspicious packages or vulnerabilities, you can report them to the relevant security teams or platforms. For this specific vulnerability, you can reach out to the Checkmarx security team at supplychainsecurity@checkmarx.com or visit their website at https://bit.ly/checkmarx-malicious-packages.
