Added 2026/10/2026-10-13-taranis.md

2026/10/2026-10-13-taranis.md

@@ -0,0 +1,101 @@
+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 [private] and copyright holder of the original "Taranis Nike Bot" software. [private] authored the original source code that is reproduced in the reported repository. The application is [private] proprietary, commercially distributed product (taranissnkrs.eu). I am filing this notice in [private] capacity as the copyright owner.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+│ The copyrighted work is the "Taranis Nike Bot" — a proprietary, commercially available
+automated software application (a "sneaker bot") written in Python. It is a complete application comprising a command-line entry point (main.py) and a modular codebase (api, cli, core, license, modules, profiles, proxies, releases, services, user, utilities) that automates checkout on sneaker-resale sites, including proprietary bypasses for bot-detection and fraud systems (Kasada, Akamai, BMP, Forter, 3DS, and POW).
+│  
+│ The work is distributed in compiled, protected form (PyArmor v8+, with string obfuscation) and
+is never distributed as source. The reported repository reproduces the entire source code of this application — the output of an unauthorized decompilation/reverse-engineering of [private] protected build — which constitutes an unlicensed reproduction and redistribution of [private] copyrighted work.
+│  
+│ The decompiled source further discloses [private] proprietary API endpoints and API keys embedded in
+the application (e.g. api/DatabaseAPI.py, core/configuration/Configuration.py, services/rpc/RPC.py, license/License.py), which [private] never made public and which are only reachable by defeating the protection.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+https://taranissnkrs.eu  
+[private]
+
+**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/ak3zaidan/PyArmor-v8-Reverse
+
+**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?**
+
+[private] copyrighted material — the source code of the Taranis Nike Bot — is not distributed in
+readable source form. It is protected by technological protection measures (TPMs) that control access to the code:
+│  
+│ - PyArmor v8+ code protection, which obfuscates the Python bytecode so it cannot be directly
+read or disassembled back into source.  
+│ - String obfuscation/encryption (PyArmor --enable-string-obfuscation), which encrypts string
+literals so embedded data (endpoints, tokens, logic strings) cannot be trivially extracted.  
+│ - Compiled/packaged binary distribution — the product ships as a compiled executable, not as
+source. The only way to read the implementation is to reverse-engineer the protected binary.
+│ - License enforcement — a license component gates access to the functionality.  
+│  
+│ Together these measures mean the only path to readable source code is to deliberately defeat
+the protection — which is exactly what the accused repository does.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The accused project is explicitly designed to circumvent those protection measures. Its README documents a deliberate process of defeating the PyArmor v8+ protection: the author built a custom decompiler, recovered the obfuscated/encrypted Python bytecode, fed bytecode snippets to LLMs to reconstruct readable source, and decrypted the obfuscated long strings, then validated the generated source against the original .pyc files. The stated purpose and output of the repository is to bypass [private] protection and redistribute the full readable source of [private] proprietary application — i.e., to strip away the very measures [private] use to control access to the code.
+
+**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:**
+
+**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.**
+
+**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.**
+
+The alleged infringer is the GitHub account ak3zaidan ([private]), identified in their [private] [private] as [private], a [private] [private] ([private]) at [private], located in [private]. Additional public identifiers: [private] — [private] and [private] — [private]. I do not have a direct email on file; the GitHub account is the infringer's primary public identifier.
+
+**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]