Malicious code in tpramcced (PyPI)

tpramcced Updated 02 Oct 2025

Summary

27/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7499: Malicious code in tpramcced (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

The tpramcced package is a PyPI package that provides functionality for [insert functionality]. It is commonly used in [insert use cases]. The package is vulnerable to a malicious code injection attack, which allows an attacker to execute spyware and steal sensitive information. This vulnerability was discovered by the Checkmarx security team.

Vulnerability Detail

The malicious code injection vulnerability in tpramcced originates from a PyPI package published by the EsqueleSquad group. The group has published nearly 6000 malicious PyPi and NPM packages, which contain spyware and information-stealing malware. The specific package that introduces the vulnerability has a SHA256 hash of 7aadf6724e3fed19e833d53b352b2184bd7c77f1d91623cadd102ce5c64fa170. The vulnerability allows an attacker to execute arbitrary code on a system where the tpramcced package is installed, 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 tpramcced

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

Conclusion

The tpramcced package in PyPI is vulnerable to a malicious code injection attack, potentially leading to unauthorized access and data theft. It is crucial to remove the affected package and replace it with a trusted version. Regularly updating and monitoring the packages used in your projects, along with employing security scanning tools like Vulert, can help mitigate such vulnerabilities. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tpramcced →

Share this vulnerability

FAQ

You can use tools like Vulert to scan your software and check for the presence of the tpramcced package with the malicious code. Vulert analyzes the Pipfile.lock file and provides real-time alerts for open-source vulnerabilities.

The malicious code in the tpramcced package can lead to unauthorized access, data theft, and the execution of additional malware on the affected system. This can result in compromised sensitive information, system instability, and potential damage to the organization.

At the time of discovery, there were no known exploits of this specific vulnerability. However, it is crucial to address the issue promptly to prevent any potential exploitation.

Due to the presence of the malicious code in the tpramcced package, it is recommended to avoid using it and instead rely on trusted alternatives. Always verify the integrity and source of the packages before including them in your projects.

Regularly monitoring security advisories, using vulnerability scanning tools like Vulert, and following best practices for secure software development can help you stay updated on security vulnerabilities in open-source packages.

How To Fix

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

pip uninstall tpramcced

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