Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

GitHub Token Leak Exposure

Written By

Rishabh Agrawal

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • GitHub Personal Access Token has been leaked in a public Docker container hosted on Docker Hub.
  • Some of the malicious packages like testbrojct2, proxyfullscraper, proxyalhttp and proxyfullscrapers work for file-matching extensions like .py, .php, .zip, .png, .jpg, and .jpeg.
  • If Python is used in any of the projects, will the above-mentioned packages be used?
  • Whether this case impact in the e-commerce implementation where the code repository is checked in Git?

Environment

  • Liferay Cloud- PaaS

Resolution

  • Liferay does not make use of Python, hence the customer environment cannot be impacted by any Python vulnerability or breach.

Additional Information

https://thehackernews.com/2024/07/github-token-leak-exposes-pythons-core.html

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?