|
| 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 | +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). |
| 10 | + |
| 11 | +--- |
| 12 | + |
| 13 | +**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.** |
| 14 | + |
| 15 | +Yes, I am authorized to act on the copyright owner's behalf. |
| 16 | + |
| 17 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 18 | + |
| 19 | +Yes |
| 20 | + |
| 21 | +**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.** |
| 22 | + |
| 23 | +3922217 |
| 24 | + |
| 25 | +**Does your claim involve content on GitHub or npm.js?** |
| 26 | + |
| 27 | +GitHub |
| 28 | + |
| 29 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 30 | + |
| 31 | +Dear GitHub team: |
| 32 | +Our company, Beijing Yidun Internet Technology Co., Ltd., as the network security service partner of CITIC Bank, is entrusted by CITIC Bank to communicate with your platform on matters related to network security. We file a complaint against the content on your platform that infringes on the intellectual property rights of CITIC Bank. |
| 33 | + |
| 34 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 35 | + |
| 36 | +1 [private] Leaked front-end code of a certain project of CITIC Bank |
| 37 | +2 https://www.github.com/geniusfuna/cs The access address of the monitoring point map of the archives of CITIC Bank Changsha Branch was leaked |
| 38 | +3 https://www.github.com/codeamateur/paysys Suspected to have leaked the abandoned warehouse of CITIC Bank's docking system, which involves account passwords for databases |
| 39 | +Infringement content description: The code file pointed to by the above link contains the name "CITIC Bank" and related data bills. This link contains infringing content: CITIC Bank and CITIC Bank. This content is used without authorization from CITIC Bank and infringes on CITIC Bank's relevant intellectual property rights. The name of CITIC Bank is an important commercial symbol that is protected by law. Any unauthorized use constitutes infringement. |
| 40 | + |
| 41 | +**If the original work referenced above is available online, please provide a URL.** |
| 42 | + |
| 43 | +[private] |
| 44 | +https://www.github.com/geniusfuna/cs |
| 45 | +https://www.github.com/codeamateur/paysys |
| 46 | + |
| 47 | +**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.** |
| 48 | + |
| 49 | +**Based on the above, I confirm that:** |
| 50 | + |
| 51 | +Specific files within the repository are infringing |
| 52 | + |
| 53 | +**Identify only the specific file URLs within the repository that is infringing:** |
| 54 | + |
| 55 | +1 [private] Leaked front-end code of a certain project of CITIC Bank |
| 56 | +2 https://www.github.com/geniusfuna/cs The access address of the monitoring point map of the archives of CITIC Bank Changsha Branch was leaked |
| 57 | +3 https://www.github.com/codeamateur/paysys Suspected to have leaked the abandoned warehouse of CITIC Bank's docking system, which involves account passwords for databases |
| 58 | + |
| 59 | +**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.** |
| 60 | + |
| 61 | +Yes |
| 62 | + |
| 63 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 64 | + |
| 65 | +Our company can provide our business license, [private] CITIC Bank business license, and authorization letter |
| 66 | + |
| 67 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 68 | + |
| 69 | +not clear |
| 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 | +**Is the work licensed under an open source license?** |
| 74 | + |
| 75 | +No |
| 76 | + |
| 77 | +**What would be the best solution for the alleged infringement?** |
| 78 | + |
| 79 | +Reported content must be removed |
| 80 | + |
| 81 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 82 | + |
| 83 | +No |
| 84 | + |
| 85 | +**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.** |
| 86 | + |
| 87 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 88 | + |
| 89 | +**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.** |
| 90 | + |
| 91 | +**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>.** |
| 92 | + |
| 93 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 94 | + |
| 95 | +[private] |
| 96 | + |
| 97 | +**Please type your full name for your signature.** |
| 98 | + |
| 99 | +[private] |
0 commit comments