Added 2025/10/2025-10-23-kryoton.md #18981
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds a DMCA takedown notice dated October 23, 2025, regarding alleged copyright infringement of a commercially licensed software project called "Krypton". The notice requests the removal of multiple GitHub repositories that allegedly contain unauthorized, reverse-engineered copies of the software.
Key Changes:
- Addition of a new DMCA takedown notice document following GitHub's standard format
- Documentation of 9 infringing repositories related to the Krypton software project
- Inclusion of standard DMCA notice elements including copyright ownership claims, technological protection measures, and legal attestations
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| **Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** | ||
|
|
||
| The original copyrighted work is Krypton, a commercially licensed software project. An unauthorized, modified version of this software has been distributed without permission, despite it being a paid product. These unauthorized distributions include reverse‑engineered and cracked copies, which infringe upon the exclusive rights of the copyright owners. |
There was a problem hiding this comment.
The filename contains a typo: 'kryoton' should be 'krypton' to match the software name referenced throughout the document.
|
|
||
| **What technological measures do you have in place and how do they effectively control access to your copyrighted material?** | ||
|
|
||
| We have a license key system, code obfuscation, and authentication in place. Due to reverse engineering, our software was reverse engineered, leaked, and subsequently distributed without permission, resulting in the current unauthorized copies and cracks. |
There was a problem hiding this comment.
[nitpick] The phrase 'Due to reverse engineering, our software was reverse engineered' is redundant. Consider rephrasing to 'Our software was reverse engineered, leaked, and subsequently distributed without permission'.
| We have a license key system, code obfuscation, and authentication in place. Due to reverse engineering, our software was reverse engineered, leaked, and subsequently distributed without permission, resulting in the current unauthorized copies and cracks. | |
| We have a license key system, code obfuscation, and authentication in place. Our software was reverse engineered, leaked, and subsequently distributed without permission, resulting in the current unauthorized copies and cracks. |
|
|
||
| **How is the accused project designed to circumvent your technological protection measures?** | ||
|
|
||
| The accused project deliberately removes or bypasses our licensekey checks and online authentication, distributes pre‑activated or patched binaries that circumvent our code obfuscation and licensing protections, and repackages the software for distribution without authorization. |
There was a problem hiding this comment.
Corrected spacing in 'licensekey' to 'license key' for consistency with line 58 where it appears as 'license key system'.
| The accused project deliberately removes or bypasses our licensekey checks and online authentication, distributes pre‑activated or patched binaries that circumvent our code obfuscation and licensing protections, and repackages the software for distribution without authorization. | |
| The accused project deliberately removes or bypasses our license key checks and online authentication, distributes pre‑activated or patched binaries that circumvent our code obfuscation and licensing protections, and repackages the software for distribution without authorization. |
This is an automated pull request to sync changes from upstream repository.
Diff summary:
A 2025/10/2025-10-23-kryoton.md