Process DMCA request

Author: dmca-sync-bot

2026/03/2026-03-25-titan-spoofer.md

@@ -0,0 +1,106 @@
+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] and copyright holder of the software known as “TITAN Spoofer,” developed under TITAN Softwork Solutions. The software was created and maintained by [private] and is distributed under the Apache 2.0 license with additional Commons Clause restrictions prohibiting commercial use without permission  
+  
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**  
+  
+The copyrighted work is a Windows-based software tool known as “TITAN Spoofer,” including its compiled binaries (TITAN Spoofer.exe and TITAN.dll) and underlying source code.  
+  
+The work includes proprietary implementations of system modification routines such as MAC spoofing, registry modification, filesystem cleaning, and WMI manipulation.  
+  
+[private] recently re-wrote TITAN Spoofer to ARES Spoofer, but TITAN Spoofer is still public and surfaces in old commits.  
+https://github.com/8damon/ARES-Spoofer-Byfron/commit/181e5a81d39758e0c81f529229bed9ea5e89aca0 <- This is TITAN Spoofer  
+You can review the repository at this point:  
+https://github.com/8damon/ARES-Spoofer-Byfron/tree/181e5a81d39758e0c81f529229bed9ea5e89aca0  
+  
+[private] also provide old releases, which are TITAN Spoofer releases, explicitly licensed, in [private] [private].  
+  
+**If the original work referenced above is available online, please provide a URL.**  
+  
+https://github.com/8damon/ARES-Spoofer-Byfron/tree/181e5a81d39758e0c81f529229bed9ea5e89aca0    
+https://github.com/8damon/ARES-Spoofer-Byfron  
+  
+**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:**  
+  
+Specific files within the repository are infringing  
+  
+**Identify only the specific file URLs within the repository that is infringing:**  
+  
+https://github.com/sashaga2a24/sentra/tree/main/assets/spoofer  
+This directory contains recompiled and renamed versions of [private] original binaries (TITAN Spoofer.exe and TITAN.dll).  
+  
+They've recompiled and renamed strings, but the PDB path in their version matches "C:\Users\admin\Downloads\Roblox-TITAN-Spoofer-Hyperion-V1.6\Release\SENTRA Spoofer.pdb", which directly references [private] original project directory and naming. Same with their DLL: C:\Users\admin\Downloads\Roblox-TITAN-Spoofer-Hyperion-V1.6\Release\SENTRA.pdb  
+  
+Further, the exported functions in their DLL match [private] original software exactly, and both their DLL and EXECUTABLE have the matching import tables to [private] software.  
+  
+The infringing software has also been distributed commercially via external platforms, including [private], without attribution and in violation of the license terms. -> [private]  
+  
+The inclusion of original debug paths (PDB references) containing [private] project name and version provides direct evidence that [private] compiled work was used without modification beyond renaming.  
+  
+**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?**  
+  
+apache-license-2.0  
+  
+**How do you believe the license is being violated?**  
+  
+They (sashaga2a24) / SENTRA are running a [private] server where they actively bundle [private] old software into their paid product. (So, commercial use, which the license explicitly forbids) -> [private]  
+  
+**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.**  
+  
+To comply with the license, the infringing party must remove all copies of [private] software (including compiled binaries and any derivative works) from the repository.  
+  
+If they wish to continue using the work, they must provide proper attribution and comply fully with the license terms, including the prohibition on commercial use without explicit permission.  
+  
+At present, the repository does not meet these requirements.  
+  
+**Do you have the alleged infringer’s contact information? If so, please provide it.**  
+  
+No.  
+  
+**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]