Malicious code in verosint (PyPI)

verosint Updated 02 Oct 2025

Summary

25/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7810: Malicious code in verosint (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Verosint is a Python package available on PyPI. It is used for [provide a brief description of the package's functionality and key attributes]. However, the package has been found to contain malicious code, as reported by Checkmarx. This code is designed to execute spyware and information-stealing malware when the package is installed or used.

Vulnerability Detail

The vulnerability in verosint arises from the presence of malicious code within the package. This code, discovered by Checkmarx's EsqueleSquad group, can lead to significant security risks. When the package is installed or used, the malicious code can execute spyware and information-stealing malware. This can result in unauthorized access to sensitive information, compromise of user privacy, and potential damage to systems and networks.

How To Fix

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

pip uninstall verosint

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 specific workaround mentioned for this vulnerability. However, as mentioned in the 'how_to_fix' section, removing the verosint package and ensuring the use of trusted packages can help mitigate the risk.

Conclusion

The presence of malicious code in the verosint package poses a significant security risk. It is crucial to promptly remove the package and any dependencies relying on it from your project. Additionally, ensure the use of trusted packages and regularly update and monitor them to mitigate the risk of similar vulnerabilities. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for verosint →

Share this vulnerability

FAQ

Verosint is a Python package available on PyPI. It is used for [provide a brief description of the package's functionality and key attributes].

The malicious code in verosint was discovered by Checkmarx's EsqueleSquad group during their analysis of PyPi and NPM packages. They found nearly 6000 malicious packages, including verosint, that executed spyware and information-stealing malware.

The presence of malicious code in verosint can lead to unauthorized access to sensitive information, compromise of user privacy, and potential damage to systems and networks.

To fix this vulnerability, it is recommended to remove the verosint package from your project and any dependencies that rely on it. Additionally, ensure that all packages used in your project are obtained from trusted sources and regularly update and monitor them.

There is no specific workaround mentioned for this vulnerability. However, removing the verosint package and using trusted packages can help mitigate the risk.

How To Fix

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

pip uninstall verosint

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