Merge pull request #20501 from github/updates

Added 2026/05/2026-05-07-radarbot.md

Author: dmca-sync-bot

2026/05/2026-05-07-radarbot.md

@@ -0,0 +1,109 @@
+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 an authorized representative of the company that owns and operates the Radarbot application and its associated backend services. Our company holds full intellectual property rights over the Radarbot mobile application, its source code, APIs, backend infrastructure, and related proprietary systems.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The copyrighted work includes the Radarbot mobile application and its proprietary backend systems, including private APIs, internal communication protocols, authentication mechanisms, and protected data structures.
+
+These systems are not सार्वजनिक and are protected by technical measures such as SSL pinning and authenticated access. The repository in question contains reverse engineered information that reproduces and exposes these proprietary API endpoints, request formats, and internal logic. It also includes instructions and tools to bypass security protections and access our services without authorization.
+
+This constitutes unauthorized reproduction and disclosure of protected elements of our software and backend services.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+The official Radarbot application is publicly available at:
+
+https://radarbot.com
+
+https://play.google.com/store/apps/details?id=com.vialsoft.radarbot_free
+
+https://apps.apple.com/app/id1099797635
+
+These public distributions do not expose or authorize access to the private APIs and internal systems described in the infringing repository.
+
+**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/OttomanZ/RadarBot24-API
+
+**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?**
+
+We implement several technological protection measures to control access to our copyrighted material and proprietary systems:
+
+SSL Pinning: Our mobile application enforces SSL pinning to prevent man-in-the-middle attacks and unauthorized interception of secure communications between the client and our servers.  
+Authentication and Session Control: Access to our backend services and APIs requires valid user authentication, session tokens, and server-side validation to ensure that only authorized clients can interact with our systems.  
+Private API Access Restrictions: Our APIs are not सार्वजनिक and are intended exclusively for use by the official Radarbot application. Requests are validated using multiple parameters, including session integrity and request structure validation.  
+Anti-Tampering Protections: The application includes protections to prevent reverse engineering, dynamic instrumentation, and modification of runtime behavior.
+
+These measures effectively restrict access to our proprietary backend services, internal logic, and protected data. The repository in question provides explicit instructions and tools to bypass these protections (including SSL pinning bypass and traffic interception), thereby enabling unauthorized access and use of our copyrighted systems.
+
+**How is the accused project designed to circumvent your technological protection measures?**
+
+The accused project is specifically designed to bypass and undermine our technological protection measures through several methods:
+
+SSL Pinning Bypass: It provides instructions and tooling (e.g., Frida scripts) to disable SSL pinning implemented in our mobile application. This allows attackers to intercept and decrypt secure HTTPS communications that are intended to be protected.  
+Traffic Interception and Analysis: The repository explains how to use tools such as Burp Suite to capture and inspect network traffic between the Radarbot app and our servers, exposing private API endpoints, request formats, and sensitive communication patterns.  
+Reverse Engineering of Private APIs: It documents internal API endpoints, parameters, headers, and authentication flows that are not publicly documented, enabling third parties to replicate legitimate client behavior outside of the authorized application.  
+Unauthorized API Access: By combining intercepted session data and reconstructed requests, the project enables direct interaction with our backend services without using the official application, bypassing authentication controls and intended access restrictions.  
+Reproduction of Proprietary Logic: The repository effectively reconstructs parts of our internal communication protocol and service structure, allowing misuse of our systems in ways that are explicitly prevented by our protections.
+
+Overall, the project does not merely analyze the application, but actively provides step-by-step guidance and tools to circumvent security protections and gain unauthorized access to our proprietary systems and copyrighted material.
+
+**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.**
+
+The alleged infringer appears to be the GitHub user:  
+[private]  
+[private]  
+[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]