Critical Malicious Code Vulnerability in tronlid Package on PyPI

tronlid Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6609: Malicious code in tronlid (PyPI). Affects tronlid versions 0.0.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tronlid package is a Python library available on the Python Package Index (PyPI) that is designed for specific functionalities within Python applications. It is utilized by developers for its ease of integration and functionality. However, the package has been identified to contain malicious code that poses significant security risks to applications that incorporate it.

Vulnerability Detail

The vulnerability identified as MAL-2025-6609 originates from the tronlid package version 0.0.1. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the systems using this package. The code was discovered by ReversingLabs and is part of a broader concern regarding the security of open-source packages, which can be compromised and used for nefarious purposes.

How To Fix

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

pip uninstall tronlid

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

As a temporary measure, avoid using the tronlid package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The tronlid package has been identified as containing malicious code that poses significant security risks. It is essential for developers to remove this package from their applications and monitor for updates or alternatives to ensure the security of their systems.

See every vulnerability recorded for tronlid →

Share this vulnerability

FAQ

Tronlid is a Python package available on PyPI, designed for specific functionalities in Python applications.

This vulnerability involves malicious code within the tronlid package that can lead to unauthorized access and exploitation of systems.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without needing to sign up.

If you are using tronlid, it is recommended to remove it immediately and look for alternative packages until a secure version is released.

Currently, there is no patched version available for the tronlid package. Monitor the package repository for updates.

How To Fix

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

pip uninstall tronlid

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