|
| 1 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are |
| 2 | +submitting this notice on behalf of a company, please be sure to use an email address on the |
| 3 | +company's domain. If you use a personal email address for a notice submitted on behalf of a |
| 4 | +company, we may not be able to process it.** |
| 5 | + |
| 6 | +Yes, I am authorized to act on the copyright owner’s behalf. |
| 7 | + |
| 8 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes |
| 9 | +to your original notice?** |
| 10 | + |
| 11 | +No |
| 12 | + |
| 13 | +**Does your claim involve content on GitHub or npm.js?** |
| 14 | + |
| 15 | +GitHub |
| 16 | + |
| 17 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 18 | + |
| 19 | +I am a [private] on the [private] at Cloudflare, Inc. I am authorized to act on Cloudflare’s behalf in |
| 20 | +connection with intellectual property matters, including copyright matters. |
| 21 | + |
| 22 | +**Please provide a detailed description of the original copyrighted work that has allegedly been |
| 23 | +infringed.** |
| 24 | + |
| 25 | +The original work is proprietary JavaScript code that Cloudflare distributes to its customers' websites with |
| 26 | +the purpose of identifying automated attacks such as bots. It is distributed in an obfuscated form that gets |
| 27 | +dynamically replaced, but contains key markers that can be used to identify it. |
| 28 | + |
| 29 | +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless |
| 30 | +the entire contents of the repository are infringing on your copyright. Please clearly state that the |
| 31 | +entire repository is infringing, OR provide the specific files within the repository you would like |
| 32 | +removed.** |
| 33 | + |
| 34 | +**Based on the above, I confirm that:** |
| 35 | + |
| 36 | +The entire repository is infringing |
| 37 | + |
| 38 | +**Identify the full repository URL that is infringing:** |
| 39 | + |
| 40 | +https://github.com/LOBYXLYX/Cloudflare-Bypass |
| 41 | +https://github.com/pagpeter/swcf |
| 42 | + |
| 43 | +**Do you claim to have any technological measures in place to control access to your copyrighted |
| 44 | +content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.** |
| 45 | + |
| 46 | +No |
| 47 | + |
| 48 | +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository |
| 49 | +and must be identified separately. Please read more about forks. As forks may often contain |
| 50 | +different material than in the parent repository, if you believe any of the repositories or files in the |
| 51 | +forks are infringing, please list each fork URL below:** |
| 52 | + |
| 53 | +The following is the list of forks from the first reported repository |
| 54 | +(https://github.com/LOBYXLYX/Cloudflare-Bypass/forks): |
| 55 | +- https://github.com/09xhbooog/Cloudflare-Bypass |
| 56 | +- https://github.com/AliAryanTech/Cloudflare-Bypass |
| 57 | +- https://github.com/ALiENxBEN/Cloudflare-Bypass |
| 58 | +- https://github.com/annihilatorrrr/Cloudflare-Bypass |
| 59 | +- https://github.com/antngdev/Cloudflare-Bypass |
| 60 | +- https://github.com/apeming/Cloudflare-Bypass |
| 61 | +- https://github.com/barcelona11/Cloudflare-Bypass |
| 62 | +- https://github.com/bgspiders/Cloudflare-Bypass |
| 63 | +- https://github.com/bipin0x01/Cloudflare-Bypass |
| 64 | +- https://github.com/bolone-sengkuni/Cloudflare-Bypass |
| 65 | +- https://github.com/c4bbage/Cloudflare-Bypass |
| 66 | +- https://github.com/catiemondon/Cloudflare-Bypass |
| 67 | +- https://github.com/chenpython/Cloudflare-Bypass |
| 68 | +- https://github.com/coders-vechai/Cloudflare-Bypass |
| 69 | +- https://github.com/COOLasHEL/Cloudflare-Bypass |
| 70 | +- https://github.com/DaniilChizhevskii/Cloudflare-Bypass-Module |
| 71 | +- https://github.com/DeaiLy/Cloudflare-Bypass |
| 72 | +- https://github.com/diagnostikon/Cloudflare-Bypass |
| 73 | +- https://github.com/edilsonynad/Cloudflare-Bypass |
| 74 | +- https://github.com/Egida/Cloudflare-Bypass |
| 75 | +- https://github.com/EmadXD/Cloudflare-Bypass |
| 76 | +- https://github.com/githubdontbanmeagain/Cloudflare-Bypass |
| 77 | +- https://github.com/gmh5225/Cloudflare-Bypass |
| 78 | +- https://github.com/guapier/Cloudflare-Bypass |
| 79 | +- https://github.com/h0useh3ad/Cloudflare-Bypass |
| 80 | +- https://github.com/hackdou/Cloudflare-Bypass |
| 81 | +- https://github.com/HadesNull123/Cloudflare-Bypass |
| 82 | +- https://github.com/herevaibhav08/Cloudflare-Bypass |
| 83 | +- https://github.com/huangsiyuan924/Cloudflare-Bypass |
| 84 | +- https://github.com/LvveI/Cloudflare-Bypass |
| 85 | +- https://github.com/huazz233/Cloudflare-Bypass |
| 86 | +- https://github.com/HungHT1890/Cloudflare-Bypass |
| 87 | +- https://github.com/huths0lo/Cloudflare-Bypass |
| 88 | +- https://github.com/Ilham311/Cloudflare-Bypass |
| 89 | +- https://github.com/IMSoley/cfcooked |
| 90 | +- https://github.com/isfans2020/Cloudflare-Bypass |
| 91 | +- https://github.com/john-peterson/Cloudflare-Bypass |
| 92 | +- https://github.com/jRodAspen/Cloudflare-Bypass |
| 93 | +- https://github.com/keef/Cloudflare-Bypass |
| 94 | +- https://github.com/Kontuzijus/Cloudflare-Bypass |
| 95 | +- https://github.com/laoziyaoshangtian/Cloudflare-Bypass |
| 96 | +- https://github.com/letruonglananh/Cloudflare-Bypass |
| 97 | +- https://github.com/lingcing/Cloudflare-Bypass |
| 98 | +- https://github.com/magdev2022/Cloudflare-Bypass |
| 99 | +- https://github.com/MaxG1/Cloudflare-Bypass |
| 100 | +- https://github.com/mhh011/Cloudflare-Bypass |
| 101 | +- https://github.com/musaspacecadet/Cloudflare-Bypass |
| 102 | +- https://github.com/mushifali/Cloudflare-Bypass |
| 103 | +- https://github.com/N-SUDY/Cloudflare-Bypass |
| 104 | +- https://github.com/notsapinho/Cloudflare-Bypass |
| 105 | +- https://github.com/p4r4xor/Cloudflare-Bypass |
| 106 | +- https://github.com/PineTang/Cloudflare-Bypass |
| 107 | +- https://github.com/ring0jke/Cloudflare-Bypass |
| 108 | +- https://github.com/sergqwer/Cloudflare-Bypass |
| 109 | +- https://github.com/SinonCute/Cloudflare-Bypass-Proxy |
| 110 | +- https://github.com/sirawats/Cloudflare-Bypass |
| 111 | +- https://github.com/unitoew/Cloudflare-Bypass |
| 112 | +- https://github.com/VertexVirtuoso/Cloudflare-Bypass |
| 113 | +- https://github.com/victorshdev/cloudflare-bypass |
| 114 | +- https://github.com/victory-volunteer/Cloudflare-Bypass |
| 115 | +- https://github.com/wxyz0001/5S-dun-Cloudflare-Bypass |
| 116 | +- https://github.com/Xiaobooooo/Cloudflare-Bypass |
| 117 | +- https://github.com/yeweilin666/Cloudflare-Bypass |
| 118 | +The following is the list of forks from the second reported repository |
| 119 | +(https://github.com/pagpeter/swcf/forks): |
| 120 | +- https://github.com/DanLev-fs/swcf |
| 121 | +- https://github.com/tigersoft6084/swcf |
| 122 | + |
| 123 | +**Is the work licensed under an open source license?** |
| 124 | + |
| 125 | +No |
| 126 | + |
| 127 | +**What would be the best solution for the alleged infringement?** |
| 128 | + |
| 129 | +Reported content must be removed |
| 130 | + |
| 131 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 132 | + |
| 133 | +For the first reported repository (https://github.com/LOBYXLYX/Cloudflare-Bypass): |
| 134 | +- User: https://github.com/LOBYXLYX |
| 135 | +- Contributors to the repository: [private] |
| 136 | +For the second reported repository (https://github.com/pagpeter/swcf): |
| 137 | +- User: https://github.com/pagpeter |
| 138 | + |
| 139 | +✅ I have a good faith belief that use of the copyrighted materials described above on the infringing |
| 140 | +web pages is not authorized by the copyright owner, or its agent, or the law. |
| 141 | + |
| 142 | +✅ I swear, under penalty of perjury, that the information in this notification is accurate and that I |
| 143 | +am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is |
| 144 | +allegedly infringed. |
| 145 | + |
| 146 | +✅ I have taken fair use into consideration. |
| 147 | + |
| 148 | +✅ I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice. |
| 149 | + |
| 150 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 151 | + |
| 152 | +[private] |
| 153 | + |
| 154 | +**Please type your full name for your signature.** |
| 155 | + |
| 156 | +[private] |
0 commit comments