github/dmca
1
Fork 0
mirror of https://github.com/github/dmca.git synced 2025-06-18 17:05:41 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Process DMCA request

Browse Source
This commit is contained in:
dmca-sync-bot 2024-12-18 22:23:35 +00:00
parent 54dcc65639
commit 3ac5749bb9
1 changed files with 141 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

141
2024/12/2024-12-17-obscuralua.md Normal file
View File

@ -0,0 +1,141 @@
Before disabling any content in relation to this takedown notice, GitHub
- 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).
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
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).
---
**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?**
Yes
**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.**
3134394
**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.**
[private] the [private] and [private] of ObscuraLua, a Lua obfuscator service. ObscuraLua's proprietary software code and related documentation are protected under copyright law. I have the authority to act on behalf of ObscuraLua in all copyright-related matters. The copyrighted work includes proprietary algorithms, encryption techniques, obfuscation logic, and source code uniquely developed by our team, which have been unlawfully reproduced and distributed.
**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.**
Dear GitHub Support,
[private] the [private] and [private] of ObscuraLua, a Lua obfuscator service offering advanced script security through proprietary encryption and obfuscation techniques. The copyrighted work includes the following:
Proprietary algorithms specifically developed for script obfuscation and encryption.
Distinct obfuscation logic and unique file structures.
Metadata and file headers that identify the obfuscated outputs as generated by ObscuraLua.
These elements are integrated into ObscuraLua software, which is only accessible to authorized users via our official platform: https://obscuralua.com.
The infringing repositories host unauthorized distributions of our proprietary obfuscation system. Specifically:
ObscuraLua-encrypted files: The files in these repositories exhibit distinctive features that match the proprietary outputs of ObscuraLua's obfuscation process, including specific patterns, encryption markers, and structures.
Unauthorized reproduction of source code: Portions of our proprietary algorithms and logic, which are not publicly available, are directly included or replicated in these repositories.
Illegitimate use of file headers and metadata: The files contain identifiable markers that indicate unauthorized access and use of ObscuraLua's obfuscator.
These repositories not only contain unauthorized copies of ObscuraLua's outputs but are also being used to facilitate unauthorized access to our obfuscator, bypassing legitimate licensing mechanisms.
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
[private]
[private]
**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.**
[private] the [private] and [private] of ObscuraLua, a Lua obfuscator service. ObscuraLua's proprietary software code and related documentation are protected under copyright law. I have the authority to act on behalf of ObscuraLua in all copyright-related matters. Unauthorized distribution, use, and modification of our obfuscator, which involves significant proprietary code, constitute direct copyright infringement.
**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.**
Dear GitHub Support,
[private] the [private] and [private] of ObscuraLua, a Lua obfuscator service that provides advanced security features for Lua scripts. The copyrighted work includes proprietary algorithms, obfuscation methods, and source code uniquely designed by our company. These elements are integrated into the ObscuraLua software, which has not been licensed for public distribution or modification.
The infringing repositories host unauthorized distributions of our proprietary ObscuraLua obfuscator, version 1.1.0, which contains significant portions of our protected source code. These repositories reproduce and distribute this code without authorization, violating our intellectual property rights.
The infringed material is identifiable by the presence of our distinct obfuscation logic, algorithmic structures, and file headers, which match the proprietary structures found in our source code. These elements are not publicly available, making their inclusion in the infringing repositories clear evidence of unauthorized use.
The original ObscuraLua software and documentation are not publicly accessible to protect against unauthorized use. However, authorized access to our platform and features is available through our official website: https://obscuralua.com.
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
https://github.com/dam737/w-azuremainad/blob/130877b42ec811d17e6b7f358955119b2c4f78ef/README.md?plain=1
https://github.com/dam737/banana-kaitun/blob/244580a78df7e84e55d1f88481a94c3aab2631b9/README.md?plain=1
https://github.com/dam737/w-azurekaitunbf/blob/2b22c24f236aff117fa369a073e99d52e8f40a68/README.md?plain=1
https://github.com/dam737/w-azurehubbountyv2/blob/d1dfb01963a9fa296beea054d44f75fa7303b241/README.md?plain=1
https://github.com/dam737/w-azurekaitunad/blob/a7d467f329c8ca3e5773da1f541907c5254bc753/README.md?plain=1
https://github.com/dam737/maru-kaitun/blob/b1b3227de0a340f17d33723e5945e2729cdace8d/README.md?plain=1
https://github.com/dam737/banana-main/blob/23f2f7f92af3e6270b62a4afcee18450a5703d95/README.md?plain=1
https://github.com/Slimexiuem/script/blob/7aff974f69ebc9bcd9a528f124511c1bcb642ebd/Redz-Hub
https://github.com/Trex277/MM2/blob/b0b311b549bc00aa68d74cf4f189f46fe2bd9e7d/MM2%20Trade%20Scam
https://github.com/dam737/w-azure-hub/blob/0619e590a02eb3e161516b2374c3a703d3286770/README.md?plain=1
https://github.com/dam737/maru-main/blob/4eb45616043bd0f8cf5b9b5165811d749ecc5fd0/README.md?plain=1
https://github.com/JoyfulTime/Rat-Hub/blob/195cac84f5f14fa77036174670ceb4970a77cd11/Games/TrollgeMultiverse#L9
https://github.com/dam737/bananakaitunav/blob/9b00326a7316676b9c5222178e7a954873f532e8/README.md?plain=1
https://github.com/luhensis/LykersHub/blob/1650689c9d73819984ca81f03a09bc51e440ec46/z-ware.lua
https://github.com/Slimexiuem/script/blob/7aff974f69ebc9bcd9a528f124511c1bcb642ebd/gun-grounds-ffa
**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.**
There are no forks of the allegedly infringing files or repositories. Therefore, no additional repositories need to be identified for takedown
**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.**
No, I do not
**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.**
Phone Number: [private]
Address: [private]
**Please type your full legal name below to sign this request.**
[private]