Malicious code in libosintsplitmc (PyPI)
Summary
MAL-2023-4275: Malicious code in libosintsplitmc (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
libosintsplitmc is a Python package available on PyPI that provides functionality for splitting multi-component OSINT data. It is commonly used in OSINT (Open Source Intelligence) projects to process and analyze data from various sources. However, this package has been found to contain malicious code, making it a potential security risk for users.
Vulnerability Detail
The libosintsplitmc 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 libosintsplitmc allows the execution of unauthorized code, which can lead to data theft, unauthorized access, and other malicious activities. The malicious code can be found in the package's dependencies and can be triggered when the 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 libosintsplitmc
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
As a workaround, you can manually inspect the code of the libosintsplitmc package and its dependencies to identify and remove any malicious code. However, this approach is time-consuming and may not guarantee complete security. It is strongly advised to follow the recommended fix and replace the package with a trusted alternative.
Conclusion
The libosintsplitmc package on PyPI has been found to contain malicious code, posing a significant security risk to projects that use it. It is crucial to remove this package and replace it with a trusted alternative. Regularly monitoring and updating your project's dependencies is essential to mitigate the risk of such vulnerabilities. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for libosintsplitmc →
FAQ
The malicious code in libosintsplitmc can lead to unauthorized code execution, data theft, and other malicious activities. It poses a significant security risk to your project and the data it handles.
You can use tools like Vulert to check if your project is affected by this vulnerability. Vulert analyzes your Pipfile.lock and alerts you in real-time for open-source vulnerabilities, including this one.
While specific exploits targeting this vulnerability may not be publicly known, the presence of malicious code in libosintsplitmc increases the risk of unauthorized access and data theft. It is crucial to address this vulnerability promptly.
While the majority of packages on PyPI and NPM are trustworthy, the presence of malicious packages highlights the importance of verifying the integrity and security of the packages you use. Regularly updating and auditing your project's dependencies is essential to mitigate such risks.
If you discover a malicious package in your project, it is recommended to remove it immediately and replace it with a trusted alternative. Additionally, consider reporting the package to the relevant package manager or security authorities to help protect other users.