Malicious code in tpintelcpuver (PyPI)

tpintelcpuver Updated 02 Oct 2025

Summary

25/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7151: Malicious code in tpintelcpuver (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 tpintelcpuver package is an open-source Python package available on PyPI. It is designed to provide information about the Intel CPU version. The package is commonly used in various Python projects to retrieve CPU information. However, the package has been found to contain malicious code.

Vulnerability Detail

The tpintelcpuver 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 tpintelcpuver allows the execution of malicious code, potentially leading 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 tpintelcpuver

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 take immediate action by removing the tpintelcpuver package and replacing it with a secure alternative.

Conclusion

The tpintelcpuver package has been compromised by the EsqueleSquad group, leading to the distribution of malicious versions of the package. To ensure the security of your project, it is crucial to remove the tpintelcpuver package and replace it with a trusted alternative. Regularly reviewing and updating the packages used in your project is also essential. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for tpintelcpuver →

Share this vulnerability

FAQ

tpintelcpuver is a Python package used to retrieve information about the Intel CPU version.

The tpintelcpuver package was compromised by the EsqueleSquad group, who published malicious versions of the package on PyPI.

The vulnerability in tpintelcpuver can lead to unauthorized access, data theft, and the execution of malicious code on affected systems.

To protect your project, remove the tpintelcpuver package and replace it with a trusted alternative. Regularly update and review the packages used in your project to ensure they are from reputable sources.

There is no direct fix available for this vulnerability. The recommended action is to remove the tpintelcpuver package and replace it with a secure alternative.

How To Fix

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

pip uninstall tpintelcpuver

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