Skip to content

Commit aa8620b

Browse files
Merge pull request #17731 from github/updates
Added 2025/05/2025-05-21-shellshock.md
2 parents 13082d5 + 9cb1a9e commit aa8620b

File tree

1 file changed

+94
-0
lines changed

1 file changed

+94
-0
lines changed

2025/05/2025-05-21-shellshock.md

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
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+
No
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 an employee of the company that holds the copyright.
28+
29+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
30+
31+
We own and develop the game Shell Shockers at https://shellshock.io/
32+
33+
Our source code is not public and no license to use, duplicate, or edit our code has been given. The infringing repository claims it is for educational purposes as a means to circumvent DMCA, but the defense is very loose and does not hold weight considering the entire repository is various ways to cheat and hack in the game. Any educational purposes of the repository are to teach how to further violate our DMCA.
34+
These cheats would not be possible without circumventing our obfuscation and injecting scripts into our game through tools such as tampermonkey or violentmonkey.
35+
36+
Taken directly from their repository:
37+
38+
[private]
39+
40+
**If the original work referenced above is available online, please provide a URL.**
41+
42+
https://shellshock.io/
43+
44+
**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.**
45+
46+
**Based on the above, I confirm that:**
47+
48+
The entire repository is infringing
49+
50+
**Identify the full repository URL that is infringing:**
51+
52+
https://github.com/hydroflame521/StateFarmClient
53+
54+
**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.**
55+
56+
Yes
57+
58+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
59+
60+
Our source code is obfuscated and the game is protected by web assembly.
61+
62+
**How is the accused project designed to circumvent your technological protection measures?**
63+
64+
The accused project is designed after deobfuscating our source code and hooking through our WASM to inject code into our game for the purposes of cheating and giving unfair advantages.
65+
66+
**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:**
67+
68+
https://github.com/Hydroflame522/StateFarmClient
69+
70+
**Is the work licensed under an open source license?**
71+
72+
No
73+
74+
**What would be the best solution for the alleged infringement?**
75+
76+
Reported content must be removed
77+
78+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
79+
80+
**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.**
81+
82+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
83+
84+
**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.**
85+
86+
**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>.**
87+
88+
**So that we can get back to you, please provide either your telephone number or physical address.**
89+
90+
[private]
91+
92+
**Please type your full name for your signature.**
93+
94+
[private]

0 commit comments

Comments
 (0)