Malicious Code in selfverosintstring (PyPI)

selfverosintstring Updated 02 Oct 2025

Summary

27/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-6743: Malicious code in selfverosintstring (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

selfverosintstring is a package available on PyPI that is used for [provide brief description of the package's functionality]. It is vulnerable to a malicious code injection that was introduced in version 0. This vulnerability allows attackers to execute spyware and information-stealing malware on systems that use this package.

Vulnerability Detail

The malicious code injection in selfverosintstring was discovered by the EsqueleSquad group. They published nearly 6000 malicious PyPi and NPM packages, including this one, which can compromise the security and privacy of affected systems. The malicious code can execute spyware and steal sensitive information from the infected systems.

How To Fix

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

pip uninstall selfverosintstring

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 a general best practice, it is recommended to review and validate the packages and dependencies used in your project before including them. This can help identify and avoid potentially malicious packages.

Conclusion

The malicious code injection in selfverosintstring poses a significant risk to the security and privacy of affected systems. It is crucial to update to a secure version of the package and regularly update all dependencies to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for selfverosintstring →

Share this vulnerability

FAQ

selfverosintstring is a PyPI package that [provide brief description of the package's functionality].

The malicious code injection in selfverosintstring allows attackers to execute spyware and steal sensitive information from the infected systems. It was introduced in version 0 of the package.

The vulnerability was discovered by the EsqueleSquad group.

The potential ramifications of this vulnerability include compromised security and privacy, as attackers can execute spyware and steal sensitive information from the infected systems.

To protect your system, it is recommended to update selfverosintstring to a version that is not affected by the malicious code injection. Regularly update all dependencies and packages in your project to ensure you are using the latest secure versions.

How To Fix

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

pip uninstall selfverosintstring

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