Added 2026/06/2026-06-24-halehound-cyd.md

2026/06/2026-06-24-halehound-cyd.md

@@ -0,0 +1,77 @@
+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 [private], the [private] [private] and copyright owner of HaleHound™-CYD, the firmware [private] publish at [private]. [private] the original application code and [private] the official compiled binaries, including the one being infringed. I am filing on [private] [private] [private] as the copyright holder.
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
+
+The original work is HaleHound-CYD version 3.6.1, [private] proprietary ESP32 firmware, distributed as the compiled binary "HaleHound-CYD-FULL.bin" only from [private] official repository at [private]. It is licensed under [private] proprietary license ("Copyright (c) [private]. All rights reserved."), which expressly prohibits "Redistributing the firmware binaries, in whole or in part, through any channel other than this repository" and "Hosting mirrors or alternative download locations for the binaries." The binary embeds [private] authorship watermark ("By: [private] ([private])"), the version string "HaleHound-CYD v3.6.1", and original modules [private] authored. It also contains compile-time file paths from [private] [private] build machine ("[private]..."), confirming it is [private] exact compiled file.
+
+**If the original work referenced above is available online, please provide a URL.**
+
+[private] (official release: [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:**
+
+Specific files within the repository are infringing
+
+**Identify only the specific file URLs within the repository that is infringing:**
+
+https://github.com/REDIHAT/halehound-x-esp32div-x-bruce/blob/main/firmware/HaleHound-CYD-FULL.bin
+
+This single file is a byte-for-byte identical copy (SHA-256: 174304ec16ce39116a7c5cbbad1745aafe3dbde9903982c79cabe6e8816950fc) of [private] proprietary HaleHound-CYD v3.6.1 binary. No other files in the repository are part of this notice.
+
+**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?**
+
+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.**
+
+GitHub user: REDIHAT ([private]). No other contact information is known to me.
+
+**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]