Malicious Code in selfvirtualinfoencode (PyPI)

selfvirtualinfoencode Updated 02 Oct 2025

Summary

26/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-6758: Malicious code in selfvirtualinfoencode (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The selfvirtualinfoencode package is an open-source Python package available on PyPI. It is used for encoding and decoding self-virtual information. This package is vulnerable to a malicious code injection attack.

Vulnerability Detail

The selfvirtualinfoencode package has been found to contain malicious code. The code was introduced in version 0 and is present in the package's source code. The malicious code is part of a larger campaign by the EsqueleSquad group, which has published nearly 6000 malicious PyPi and NPM packages. These packages execute spyware and information-stealing malware. The specific impact of the malicious code in selfvirtualinfoencode is not mentioned in the vulnerability details.

How To Fix

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

pip uninstall selfvirtualinfoencode

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. The best course of action is to follow the recommended fix and remove the selfvirtualinfoencode package.

Conclusion

The selfvirtualinfoencode package has been found to contain malicious code. It is recommended to remove this package from your project and replace it with a trusted alternative. Regularly updating and reviewing the packages used in your project is also important to avoid using any known malicious packages. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for selfvirtualinfoencode →

Share this vulnerability

FAQ

The selfvirtualinfoencode package is a Python package used for encoding and decoding self-virtual information.

The malicious code was introduced in version 0 of the selfvirtualinfoencode package. It is part of a larger campaign by the EsqueleSquad group.

The specific impact of the malicious code in selfvirtualinfoencode is not mentioned in the vulnerability details.

To fix this vulnerability, it is recommended to remove the selfvirtualinfoencode package from your project and replace it with a trusted alternative.

To prevent using known malicious packages, it is important to regularly update and review the packages used in your project.

How To Fix

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

pip uninstall selfvirtualinfoencode

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