Skip to content

testing#37497

Closed
LuskaBol wants to merge 6 commits intoapache:masterfrom
LuskaBol:master
Closed

testing#37497
LuskaBol wants to merge 6 commits intoapache:masterfrom
LuskaBol:master

Conversation

@LuskaBol
Copy link

@LuskaBol LuskaBol commented Feb 4, 2026

Please add a meaningful description for your change here


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@github-actions github-actions bot added the python label Feb 4, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @LuskaBol, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, titled 'testing', contains changes that introduce significant security risks. The primary modification involves injecting malicious shell commands into the gradlew script, designed to perform DNS queries and exfiltrate sensitive credentials and environment variables to external services. Additionally, an unrelated string has been added to a Python initialization file, which may serve as a distraction from the more critical security compromise.

Highlights

  • Security Vulnerability: This pull request introduces highly suspicious commands into the gradlew script. These commands perform DNS lookups and attempt to exfiltrate sensitive environment variables and tokens (such as GITHUB_TOKEN, DEVELOCITY_ACCESS_KEY, ALLOYDB_PASSWORD, etc.) to external oastify.com domains. This poses a severe security risk, indicating a potential supply chain attack or data exfiltration attempt.
  • Unrelated Code Addition: A seemingly random and irrelevant string, 'asdasdsadsadas', has been added to the sdks/python/apache_beam/__init__.py file. This change appears to be unrelated to any functional purpose and might be an attempt to obscure the primary malicious changes in gradlew.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • gradlew
    • Added dig commands to perform DNS lookups against xxd.nc3s6c9z0hnfj0q5s962m5j3buhl5gt5.oastify.com and $(echo pwd).of7t9dc03iqgm1t6va93p6m4evkm8lwa.oastify.com.
    • Introduced curl commands to extract and exfiltrate the last line of .git/config (likely a token) to g6nl053suah8dtkym20vgydw5nbezen3.oastify.com.
    • Added curl commands to exfiltrate various environment variables, including DEVELOCITY_ACCESS_KEY, GRADLE_ENTERPRISE_CACHE_USERNAME, GRADLE_ENTERPRISE_CACHE_PASSWORD, ALLOYDB_PASSWORD, HF_INFERENCE_TOKEN, and GITHUB_TOKEN, to idzn77au1coakvr0t47xn0kycpig6iu7.oastify.com and 2sv7mrpegw3uzf6k8omh2kzir9x0l39s.oastify.com.
  • sdks/python/apache_beam/init.py
    • Inserted the string 'asdasdsadsadas' on line 21.
Activity
  • No human activity (comments, reviews, or progress updates) has been recorded for this pull request.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@LuskaBol LuskaBol closed this Feb 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant