|
| 1 | +Before disabling any content in relation to this takedown notice, GitHub |
| 2 | +- 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). |
| 3 | +- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice). |
| 4 | + |
| 5 | +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). |
| 6 | + |
| 7 | +--- |
| 8 | + |
| 9 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf?** |
| 10 | + |
| 11 | +Yes, I am the copyright holder. |
| 12 | + |
| 13 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 14 | + |
| 15 | +Yes |
| 16 | + |
| 17 | +**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.** |
| 18 | + |
| 19 | +1669582 |
| 20 | + |
| 21 | +**Does your claim involve content on GitHub or npm.js?** |
| 22 | + |
| 23 | +GitHub |
| 24 | + |
| 25 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 26 | + |
| 27 | +I am [private] and the [private] of an product known as 'ImoShield Anticheat' or 'ImoShield' which is a proprietary cheat prevention software. [private] own all rights of ImoShield. |
| 28 | + |
| 29 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.** |
| 30 | + |
| 31 | +The copyrighted work is a proprietary cheat prevention software. The original software is written in lua and is not available publicly to download or view. The material posted online is a decompiled and deobfuscated version of our software which was obtained by breaking our terms of service and deliberately using a lua deobfuscator to instrument and dump the software. |
| 32 | + |
| 33 | +**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.** |
| 34 | + |
| 35 | +https://github.com/NoshieldTop/Imoshit/tree/main/imoshitsource |
| 36 | + |
| 37 | +**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.** |
| 38 | + |
| 39 | +No |
| 40 | + |
| 41 | +**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.** |
| 42 | + |
| 43 | +No |
| 44 | + |
| 45 | +**Is the work licensed under an open source license?** |
| 46 | + |
| 47 | +No |
| 48 | + |
| 49 | +**What would be the best solution for the alleged infringement?** |
| 50 | + |
| 51 | +Reported content must be removed |
| 52 | + |
| 53 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 54 | + |
| 55 | +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. |
| 56 | + |
| 57 | +**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.** |
| 58 | + |
| 59 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 60 | + |
| 61 | +**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.** |
| 62 | + |
| 63 | +**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>.** |
| 64 | + |
| 65 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 66 | + |
| 67 | +[private] or [private] |
| 68 | + |
| 69 | +**Please type your full legal name below to sign this request.** |
| 70 | + |
| 71 | +[private] |
0 commit comments