**Are you the copyright holder or authorized to act on the copyright owner's behalf?**

Yes, I am the copyright holder.

**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**

No

**Does your claim involve content on GitHub or npm.js?**

GitHub

**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**

I can confirm that the organization holds the exclusive rights and ownership over all content within its private [private] repositories. The unauthorized access and subsequent leak of this content is a clear violation of the organization's intellectual property rights and the company will take all necessary legal action to protect these rights.

The organization has the full authority to act on behalf of its owners in all matters related to the protection of its intellectual property, including, but not limited to, the enforcement of its copyrights.

In accordance with applicable laws, including the Digital Millennium Copyright Act (DMCA), the company will actively pursue all individuals or entities who have illegally obtained and/or shared the leaked content.

This statement serves as official notice that the company takes the protection of its intellectual property very seriously and will not hesitate to take legal action to protect its rights.

**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.**

All of the repositories listed and posted by this user were stolen through an organization member and were listed as private. All of the repositories uploaded by this user belong to the following organizations;

[private]  

Private repository links to the specifically leaked repositories are;  
[private]  
[private]  

**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**

Each leaked repository is 1:1 to the private organization repositories, List;

https://github.com/fork1488/be-bypass  
https://github.com/fork1488/eac-bypass

**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.**

No

**<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.**

Yes I have. All of the leaked repositories were pulled on the date of December 11th, 2022.

**Is the work licensed under an open source license?**

No

**What would be the best solution for the alleged infringement?**

Reported content must be removed

**Do you have the alleged infringer’s contact information? If so, please provide it.**

Name: [private]  
Address: [private]  
Number: [private]  

**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.**

**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**

**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.**

**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>.**

**So that we can get back to you, please provide either your telephone number or physical address.**

[private]

**Please type your full legal name below to sign this request.**

[private]
