Malicious code in splitsplit (PyPI)

splitsplit Updated 02 Oct 2025

Summary

25/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-6810: Malicious code in splitsplit (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

splitsplit is a package available on PyPI, which is the Python Package Index. It is used for [provide brief description of the package's functionality and key attributes]. Unfortunately, splitsplit has been found to contain malicious code, making it vulnerable to security threats.

Vulnerability Detail

The splitsplit package has been identified as containing malicious code by the EsqueleSquad group. This group has published nearly 6000 malicious PyPi and NPM packages, which execute spyware and information-stealing malware. The specific details of the vulnerability can be found in the Checkmarx report with SHA256 hash 4f6408395479540590e72009900b7a38ff7853c11c87812a93ac0157666dd56d. This vulnerability poses a significant risk to systems that have installed the splitsplit package, as it can lead to unauthorized access, data theft, and other malicious activities.

How To Fix

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

pip uninstall splitsplit

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 splitsplit package and follow the recommended steps to fix the issue.

Conclusion

The splitsplit package on PyPI has been found to contain malicious code, posing a significant security risk to systems that have installed it. It is crucial to remove the package and follow the recommended steps to fix the vulnerability. Regular software updates and security measures are essential to prevent similar issues in the future. For further support and guidance, please contact DevNack.com.

See every vulnerability recorded for splitsplit →

Share this vulnerability

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 the malicious code in splitsplit.

The malicious code in splitsplit can lead to unauthorized access to sensitive information, data theft, and the execution of additional malware on the affected system. It is crucial to take immediate action to mitigate these risks.

Yes, the recommended fix is to remove the splitsplit package from your system. Additionally, it is important to regularly update and patch your software to prevent similar vulnerabilities in the future.

This vulnerability was discovered by Checkmarx, a security company specializing in software vulnerability detection. They have provided detailed information about the malicious code in splitsplit.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability and other security concerns.

How To Fix

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

pip uninstall splitsplit

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