Malicious code in tpencodecandyosint (PyPI)

tpencodecandyosint Updated 02 Oct 2025

Summary

26/02/2023
CRITICAL
No i
Critical
Not published

MAL-2023-7012: Malicious code in tpencodecandyosint (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

tpencodecandyosint is a package available on PyPI that provides functionality for encoding and decoding candy-related data. It is commonly used in Python projects that involve candy-related operations. However, this package has been found to contain malicious code, which poses a significant security risk to applications that use it.

Vulnerability Detail

The tpencodecandyosint 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 tpencodecandyosint allows attackers to gain unauthorized access to sensitive information and potentially compromise the entire system. The malicious code can be triggered when using certain functions or methods provided by the package.

How To Fix

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

pip uninstall tpencodecandyosint

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 remove tpencodecandyosint and thoroughly scan your codebase to ensure the removal of any traces of the malicious code.

Conclusion

The tpencodecandyosint package has been compromised and contains malicious code. It is crucial to remove this package from your project dependencies and thoroughly scan your codebase for any traces of the malicious code. Additionally, it is recommended to use a reputable security tool like Vulert to scan your code for other vulnerabilities and ensure the overall security of your application. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for tpencodecandyosint →

Share this vulnerability

FAQ

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your Pipfile.lock, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are detected.

The consequences of this vulnerability can be severe. Attackers can gain unauthorized access to sensitive information, compromise the system, and potentially install spyware or other malware. This can lead to data breaches, privacy violations, and financial losses.

No, there is no fix available for tpencodecandyosint. The package itself has been compromised, and the only solution is to remove it from your project dependencies and thoroughly scan your codebase for any traces of the malicious code.

While PyPI is generally a reliable source for packages, this incident highlights the importance of exercising caution and performing regular security checks. It is recommended to use reputable security tools, like Vulert, to scan your code and identify any potential vulnerabilities or malicious packages.

To prevent similar incidents in the future, it is crucial to follow best practices for package management and security. Regularly update your dependencies, use reputable sources for packages, and employ security tools to scan your code for vulnerabilities. Additionally, staying informed about the latest security threats and vulnerabilities can help you take proactive measures.

How To Fix

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

pip uninstall tpencodecandyosint

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