Added 2026/05/2026-06-01-mlsac.md

2026/05/2026-06-01-mlsac.md

@@ -0,0 +1,112 @@
+Before disabling any content in relation to this takedown notice, GitHub
+- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
+- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
+
+To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
+
+---
+
+**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**
+
+Yes, I am the copyright holder.
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
+
+No
+
+**Does your claim involve content on GitHub or npm.js?**
+
+GitHub
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
+
+I am the [private], [private], and [private] copyright holder of the "MLSAC" project. [private] [private] the vast majority of the source code, including a core commit consisting of approximately 9,000 lines of original code. The project is managed by the "MLSAC [private]" which [private] [private]. I have full legal authority to protect this intellectual property and ensure compliance with its licensing terms.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The copyrighted work is the client-side component (Minecraft plugin) of the "MLSAC" Cloud-Based Anti-Cheat system. This plugin serves as a sensor that collects data and communicates with a proprietary cloud backend for AI-powered analysis. The work includes original Java source code, networking logic for secure API communication, and data collection algorithms. The original codebase, characterized by a foundational commit of ~9,000 lines, is hosted at: https://github.com/MLSAC/client-side. All files contain the "Copyright (C) 2026 MLSAC Team" headers.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+https://github.com/MLSAC/client-side
+
+**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**
+
+**Based on the above, I confirm that:**
+
+The entire repository is infringing
+
+**Identify the full repository URL that is infringing:**
+
+https://github.com/SoMax1soft/MLSAC
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
+
+No
+
+**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**
+
+**Is the work licensed under an open source license?**
+
+Yes
+
+**Which license?**
+
+gnu-general-public-license-v3.0
+
+**How do you believe the license is being violated?**
+
+The infringer has committed multiple willful violations of the GPLv3 license:
+
+1. Section 5(a) - No modification notices: The source files were copied directly from the original MLSAC codebase, which carries "Copyright (C) 2026 MLSAC Team" headers throughout. The infringer re-uploaded these files without adding any notices indicating which files were changed or when, which is a direct violation of GPLv3 Section 5(a).
+
+2. False claim of official status: The infringer's README presents the repository as the official MLSAC repository. This is false. The original official repository is at https://github.com/MLSAC/client-side.
+
+3. Using the identical project name: The repository is named "MLSAC" - the same name as the original project. This is a deliberate attempt to pass off the repository as legitimate or official.
+
+4. Misrepresenting authorship: [private] authored approximately 9,000 lines of the core codebase. The copyright headers in every file reflect this. The infringer presents the work as their own.
+
+Prior notification: [private] published a public notice in the official [private] project channel clearly stating that the infringer had violated the GPLv3 license and that their rights under the license had been terminated. The infringer demonstrably read this - I have screenshots of him reacting to it in private messages to mutual contacts, mocking the notice. He cannot claim he was unaware of the termination.
+
+Infringer's response and deletion of evidence: After reading the notice, the infringer published a public statement claiming that [private] invocation of GPLv3 Section 8 was "questionable" and should not be taken seriously. This post has since been deleted by the infringer. I have a saved copy. Around the same time, the infringer posted in their [private] channel acknowledging that their [private] account had been frozen, stating they were "working on it." That post was also deleted. I have a saved copy of that as well. The deletion of both posts after the dispute escalated is a clear attempt to remove evidence.
+
+Commercial exploitation under a terminated license: The infringer is actively selling paid subscriptions to a cloud-based anti-cheat service marketed under the "MLSAC" name. This service does not function without the client-side plugin - the very plugin that infringes on [private] copyright. The infringer is therefore generating direct commercial revenue from software they no longer have any legal right to distribute. They were notified, publicly dismissed the termination, deleted the evidence, and kept selling.
+
+[private] ban: The infringer was banned from the [private] marketplace. They publicly acknowledged this in their [private] channel before deleting the post. This is consistent with a pattern of bad-faith conduct and disregard for platform rules and legal obligations.
+
+History of this DMCA submission: This is a resubmission. I filed an initial DMCA notice about this same repository. GitHub [private] replied asking me to clarify what changes the infringer could make to come into compliance. I submitted a revised notice addressing that. Six days passed with no further response and no action. As of today, the infringing repository has been publicly accessible for 11 days. This notice fully addresses the clarifications previously requested by GitHub [private].
+
+License termination under GPLv3 Section 8: Under GPLv3 Section 8, any violation of the license automatically terminates the violator's rights. The 30-day cure window is only available to parties who have not previously received notice of a violation. The infringer received clear and public notice, acknowledged it by reacting to it, dismissed it, and continued the violations. I hereby explicitly and finally terminate this user's license under GPLv3 Section 8(a). This termination is permanent and I am not granting reinstatement under any circumstances.
+
+**What changes can be made to bring the project into compliance with the license? For example, adding attribution, adding a license, making the repository private.**
+
+For the record, the changes that would have been required are:
+
+1. Add proper modification notices to every changed file stating what was changed and when, as required by GPLv3 Section 5(a).  
+2. Remove any claim that the repository is official or affiliated with the original MLSAC project.  
+3. Rename the repository so it no longer impersonates the original project name.
+
+None of this is relevant anymore. The infringer was notified, publicly rejected the notice, deleted the evidence, and kept selling subscriptions. Their license has been explicitly and finally terminated under GPLv3 Section 8(a). The only acceptable outcome is the complete and permanent removal of the repository.
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+I only have the infringer's social media contact information:   
+[private]: [private] & [private]  
+[private]: [private]
+GitHub Profile: [private]
+
+**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
+
+**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
+
+**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
+
+**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
+
+**So that we can get back to you, please provide either your telephone number or physical address.**
+
+[private]
+
+**Please type your full name for your signature.**
+
+[private]