|
| 1 | +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). |
| 2 | + |
| 3 | +--- |
| 4 | + |
| 5 | +**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.** |
| 6 | + |
| 7 | +Yes, I am the copyright holder. |
| 8 | + |
| 9 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 10 | + |
| 11 | +Yes |
| 12 | + |
| 13 | +**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.** |
| 14 | + |
| 15 | +3334482 |
| 16 | + |
| 17 | +**Does your claim involve content on GitHub or npm.js?** |
| 18 | + |
| 19 | +GitHub |
| 20 | + |
| 21 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 22 | + |
| 23 | +I am the [private] and [private] of the proprietary software "Raven B4". I am submitting this takedown on behalf of my organization, which distributes this software commercially. |
| 24 | + |
| 25 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 26 | + |
| 27 | +Raven B4 is a paid, closed-source Minecraft modification ("client") that [private] originally developed and continue to maintain. It enhances Minecraft gameplay with advanced features such as automation, visual enhancements, and utility modules. It is proprietary software that has never been publicly released as source code or under any open-source license. Raven B4 is distributed exclusively through our [private] [private] server to verified customers who have purchased a license. |
| 28 | + |
| 29 | +The software is promoted on our official [private] at [private], where users can also find a link to our [private] in the video descriptions to inquire about purchasing access. We also advertise Raven B4 on a second channel at [private], which links directly to our sales [private] at [private]. |
| 30 | + |
| 31 | +A third-party project hosted at https://github.com/Strangerrrs/Raven-bS and called “Raven bS” has published a version of Raven B4 that is based on decompiled and deobfuscated proprietary source code. The repository's README openly admits this by stating: |
| 32 | + |
| 33 | +“Raven B4, but for those who can't afford it, or too paranoid to get it… based off b3, with the help of b4 src.” |
| 34 | + |
| 35 | +This is a clear acknowledgement that the codebase was derived from unauthorized access to Raven B4’s source code. Additionally, the Raven bS [private] server (linked directly from the GitHub README: [private]) includes a message from the [private], “[private],” who explicitly states in the FAQ: |
| 36 | + |
| 37 | +“b4 src refers to decompiled, deobfuscated, and remapped Raven b4 Update 2 code.” |
| 38 | + |
| 39 | +This is a direct admission that the developer used illegally obtained source code from Raven B4, which was leaked and deobfuscated from a cracked version publicly posted at [private]. A screenshot of this admission is available at: [private]. |
| 40 | + |
| 41 | +The features, structure, and naming conventions of the “Raven bS” repository are substantially similar to Raven B4, reinforcing that it is a derivative, unauthorized version of our protected software. |
| 42 | + |
| 43 | +**If the original work referenced above is available online, please provide a URL.** |
| 44 | + |
| 45 | +**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.** |
| 46 | + |
| 47 | +**Based on the above, I confirm that:** |
| 48 | + |
| 49 | +The entire repository is infringing |
| 50 | + |
| 51 | +**Identify the full repository URL that is infringing:** |
| 52 | + |
| 53 | +https://github.com/Strangerrrs/Raven-bS |
| 54 | + |
| 55 | +**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.** |
| 56 | + |
| 57 | +Yes |
| 58 | + |
| 59 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 60 | + |
| 61 | +We use a Hardware ID (HWID)-based authentication system to control access to our software. When a user purchases Raven B4, their unique HWID is whitelisted and stored in our secure database. Our custom loader verifies the user's HWID during login, and only if the HWID is authorized the client is loaded from our server. Our API servers, which handle authentication and validation, are hosted at https://daikirai.xyz/ for this purpose. In addition, the software is protected using code obfuscation to prevent reverse engineering and tampering. |
| 62 | + |
| 63 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 64 | + |
| 65 | +The accused project has knowingly and deliberately circumvented our technological protection measures by using a decompiled and deobfuscated version of Raven B4’s proprietary source code — obtained without authorization through a cracked leak. In the process, they have completely removed our HWID-based authentication system, which is used to verify legitimate users and prevent unauthorized access. They have also stripped all obfuscation layers that were implemented to prevent reverse engineering and code tampering. |
| 66 | + |
| 67 | +These actions have effectively disabled the core mechanisms we use to protect Raven B4 against piracy. The modified version, rebranded as “Raven bS,” is being publicly distributed on GitHub, allowing unrestricted access to what is essentially a pirated copy of our paid software. This not only enables widespread, unauthorized use but also allows others to build upon and redistribute our stolen intellectual property, further compounding the infringement. |
| 68 | + |
| 69 | +The project's README and developer statements in the associated Discord server explicitly confirm that they used "decompiled, deobfuscated, and remapped Raven B4 Update 2 code" to create their version, fully acknowledging that they bypassed our protection mechanisms to repurpose and redistribute stolen code. |
| 70 | + |
| 71 | +**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:** |
| 72 | + |
| 73 | +https://github.com/lquifii/RavenBS-Plus |
| 74 | +https://github.com/q1/raven-bs-alpha |
| 75 | + |
| 76 | +**Is the work licensed under an open source license?** |
| 77 | + |
| 78 | +No |
| 79 | + |
| 80 | +**What would be the best solution for the alleged infringement?** |
| 81 | + |
| 82 | +Reported content must be removed |
| 83 | + |
| 84 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 85 | + |
| 86 | +**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.** |
| 87 | + |
| 88 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 89 | + |
| 90 | +**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.** |
| 91 | + |
| 92 | +**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>.** |
| 93 | + |
| 94 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 95 | + |
| 96 | +[private] |
| 97 | + |
| 98 | +**Please type your full name for your signature.** |
| 99 | + |
| 100 | +[private] |
0 commit comments