Process DMCA request

Author: dmca-sync-bot

2026/05/2026-05-06-modders-multitool-3.md

@@ -0,0 +1,81 @@
+**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 copyright holder.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+A utility for quickly generating Baldur's Gate 3 mod packs from an unpacked workspace, along with a long list of other features that aid in this process.
+
+The license is not open source, it is source available, which is an important distinction (https://github.com/ShinyHobo/BG3-Modders-Multitool?tab=License-1-ov-file#readme):
+
+"This software is source available, not open source. Redistribution, and modification for private or public use, without express permission from the copyright owner, is prohibited.
+
+Baldur's Gate 3 Modder's Multitool is unofficial fan content, not approved/endorsed by Larian Studios. Portions of the materials used are property of [private] and [private].
+
+[private] is owned by [private] and utilized under the MIT license."
+
+The fork has a modification branch that violates [private] license: https://github.com/nandez/BG3-Modders-Multitool/tree/poc/linux-port
+
+I did not give this person permission, therefore they are in violation of the terms of the license. There are 39 forks of [private] project; I made this DMCA because this specific one is in violation.
+
+[private] license says you can't modify the code, and it has been modified. It is in violation of the license, not just a simple fork.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+https://github.com/ShinyHobo/BG3-Modders-Multitool
+
+**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/nandez/BG3-Modders-Multitool
+
+**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:**
+
+https://github.com/nandez/BG3-Modders-Multitool
+
+**Is the work licensed under an open source license?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+**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]

2026/05/2026-05-06-research-materials-2.md

@@ -0,0 +1,94 @@
+While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s).
+
+---
+
+**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 copyright owner of the proprietary software mentioned below. This is a follow-up/supplemental notice to my previous successful takedown (Original Ticket ID: 4309175).
+
+I am requesting the immediate removal of the additional infringing repositories listed below. The infringing code and its fork networks are spreading rapidly across GitHub, and these repositories contain the exact same copyrighted material that was already verified and removed under the previous ticket.
+
+Please apply the same takedown action to these links to prevent further unauthorized distribution
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The original copyrighted work is a proprietary software research framework consisting of a specific collection of C++ source files, headers, and build scripts. The framework includes unique implementations of the following components:
+
+Custom Logger and Hooking System: Proprietary logic for event interception and data logging.
+
+Internal Tools: Import fixers, memory dispatcher fixes, and HWID/system spoofs.
+
+Cryptographic & Execution Logic: Custom SHA-256 implementation fixes and entry execution stubs.
+
+The copyright belongs to [private].
+
+The infringing repository is a direct, unauthorized copy of my private work. This is proven by the identical project file structure, specific filenames (e.g., fix_dump.cpp, ROADMAP.txt, neverlosesdk.hpp, cpuid_emu_0.h, mem_dispatcher.cpp), and the unique coding style/logic within these files, which matches [private] original private repository perfectly.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+**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/Slaughterhouse-dev/Neverloose  
+https://github.com/exhor-dev/girlyboys.net
+
+**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.**
+
+Yes
+
+**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
+
+The copyrighted material was protected by [private]’s access control infrastructure. It was stored within a Private Repository, which effectively restricts access to authorized users only through secure authentication (password protection and SSH/Personal Access Tokens).
+
+These measures effectively controlled access by ensuring the code was not indexed, not public, and only accessible via [private] verified account credentials. The unauthorized distribution occurred because these access controls were bypassed through a compromise of [private] personal account security.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The accused project is not designed to technically circumvent encryption within the files themselves, but it represents the direct result of bypassing [private]'s private repository access controls.
+
+By re-hosting [private] proprietary source code in a public repository, the infringer has effectively circumvented the 'Private' status and authentication requirements [private] had in place. This unauthorized publication makes [private] private intellectual property accessible to the public without the need for the credentials or permissions that were originally required to view it.
+
+**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?**
+
+No
+
+**What would be the best solution for the alleged infringement?**
+
+Reported content must be removed
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**
+
+**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]