Skip to content

Commit fe6a323

Browse files
Merge pull request #19003 from github/updates
Added 2025/10/2025-10-28-blue-archive.md
2 parents dde66eb + da17cd2 commit fe6a323

1 file changed

Lines changed: 165 additions & 0 deletions

File tree

2025/10/2025-10-28-blue-archive.md

Lines changed: 165 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,165 @@
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+
**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.**
10+
11+
Yes, I am authorized to act on the copyright owner's behalf.
12+
13+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
14+
15+
Yes
16+
17+
**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.**
18+
19+
2913464
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 agent authorized to act on behalf of the owner, of certain intellectual property rights ("NEXON [private]");
28+
29+
※ NEXON [private] has given the power of attorney to DAZIUNDA, LLC. to respond to unlawful and infringing behavior on ‘Blue Archive’.
30+
31+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
32+
33+
Blue Archive is a popular free-to-play action RPG developed by NEXON [private]. It features strategic gameplay and anime-style graphics, allowing players to choose from various characters, each with unique abilities and storylines, to embark on quests, battle enemies, and engage in PvP combat. The game offers a mix of PvE and PvP elements, along with extensive customization options for characters and equipment.
34+
35+
For more information, visit the official website: https://bluearchive.nexon.com/
36+
37+
**If the original work referenced above is available online, please provide a URL.**
38+
39+
https://bluearchive.nexon.com/
40+
41+
**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.**
42+
43+
**Based on the above, I confirm that:**
44+
45+
The entire repository is infringing
46+
47+
**Identify the full repository URL that is infringing:**
48+
49+
https://github.com/SyauqiMA/SCHALE.GameServer
50+
https://github.com/170warship/SCHALE.GameServer
51+
https://github.com/LunaticQuantum-dream/SCHALE.GameServer
52+
https://github.com/a731385540/SCHALE.GameServer
53+
https://github.com/ycxom/SCHALE.GameServer
54+
https://github.com/Kisegami/SCHALE.GameServer
55+
https://github.com/DefSw0rd/SCHALE.GameServer
56+
https://github.com/jounat/SCHALE.GameServer
57+
https://github.com/realCreeper938/SCHALE.GameServer
58+
https://github.com/estlio/SCHALE.GameServer
59+
https://github.com/szechnaya/SCHALE.GameServer
60+
https://github.com/ShenaiSmile/SCHALE.GameServer
61+
https://github.com/Peagger/SCHALE.GameServer
62+
https://github.com/Ryou-Kaze/SCHALE.GameServer
63+
https://github.com/xzr0736/SCHALE.GameServer
64+
https://github.com/lmm258/SCHALE.GameServer
65+
https://github.com/xnqycs/SCHALE.GameServer
66+
https://github.com/kategawa3/SCHALE.GameServer
67+
https://github.com/JFYoung01/SCHALE.GameServer
68+
https://github.com/xiaofeiTM233/RE.SCHALE.GameServer
69+
https://github.com/daizhuentou/SCHALE.GameServer
70+
https://github.com/AzureXuanVerse/GameServer.SCHALE
71+
https://github.com/shunner114514/SCHALE.GameServer_USE
72+
https://github.com/SunsetMkt/SCHALE.GameServer
73+
https://github.com/AzureXuanVerse/SCHALE.GameServer
74+
https://github.com/ClayCoffee/SCHALE.GameServer
75+
https://github.com/NewblyAaron/SCHALE.GameServer
76+
https://github.com/limouren1145141919810/SCHALE.GameServer
77+
https://github.com/AlphaAntivoid/SCHALE.GameServer
78+
https://github.com/yuurichan/GameServer
79+
https://github.com/AzureXuanVerse/RE.SCHALE.GameServer
80+
https://github.com/irecns/RE.SCHALE.GameServer
81+
https://github.com/suna-aquatope/Sensei
82+
https://github.com/TangHuLuTaiTian/RE.SCHALE.GameServer
83+
https://github.com/wcmjty/RE.SCHALE.GameServer
84+
https://github.com/ycxom/copy.SCHALE.GameServer
85+
https://github.com/A-Archives-and-Forks/SCHALE.GameServer-
86+
https://github.com/minhh2792/SCHALE.GameServer
87+
https://github.com/O-G-F/SCHALE.GameServer
88+
https://github.com/Xiaomckedou233/SCHALE.GameServer
89+
https://github.com/Yuneet/SCHALE.GameServer
90+
https://github.com/Zenchar/SCHALE.GameServer
91+
https://github.com/David205x/GameServer.SCHALE
92+
https://github.com/fangmachuan/GameServer.SCHALE
93+
https://github.com/Hollow468/GameServer.SCHALE
94+
https://github.com/irecns/SCHALE.GameServer_USE
95+
https://github.com/O-G-F/SCHALE.GameServer_USE
96+
https://github.com/Ashtorri/SCHALE.GameServer
97+
98+
**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.**
99+
100+
Yes
101+
102+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
103+
104+
Blue Archive APK employs several Technical Protection Measures (TPM) to safeguard its integrity and protect against unauthorized access and manipulation. These measures include:
105+
106+
1. Debugger Detection: To prevent tools like Frida from monitoring and manipulating the application's runtime state, Blue Archive includes mechanisms to detect debuggers. This helps maintain the application's integrity and prevent malicious actions.
107+
108+
2. Emulator Detection: Blue Archive has features to detect if the application is running within an emulator. Emulators replicate the hardware and software environment of a mobile device, allowing attackers to analyze and manipulate the app's behavior. By detecting emulators, the application can prevent execution in such environments​​.
109+
110+
3. Method Hooking Prevention: Method hooking allows malicious users to intercept and alter specific function calls within the application. Blue Archive includes security mechanisms to detect and prevent such hooking attempts, ensuring that the application's code execution remains secure and unaltered​.
111+
112+
4. App Integrity Check: Blue Archive performs integrity checks to detect any tampering with its code. This helps prevent the insertion of malicious code or unauthorized modifications to the application.
113+
114+
5. Network Security: To protect against Man-in-the-Middle (MitM) attacks, Blue Archive uses encrypted communication and robust server authentication. This ensures that data transmitted between the user and the server remains secure and cannot be intercepted or altered by attackers​​.
115+
116+
**How is the accused project designed to circumvent your technological protection measures?**
117+
118+
Previously, I submitted a DMCA notice that identified a repository and specific files under the GitHub user [private] which included [private]-based scripts and source code used to bypass technical protection measures and to redirect traffic from official NEXON [private] servers to unauthorized private servers. Those URLs (hosted under [private]) have since been removed by GitHub and are no longer reachable.
119+
120+
However, despite removal of the original [private] URLs, copies, forks, and other repositories remain active and continue to distribute or enable:
121+
122+
- Source code files that utilize Frida to manipulate and redirect network traffic from NEXON [private]’s official servers to unauthorized private servers. Example of previously-observed file (now removed):
123+
- [private] (deleted)
124+
125+
*[private] is an open-source dynamic instrumentation toolkit that allows users to inject scripts into running applications for the purposes of analysis, debugging, and modification. It is commonly used by security researchers and reverse engineers to interact with and manipulate software in real-time.
126+
127+
- Scripts and documentation describing how to modify NEXON [private]’s Blue Archive application to bypass authentication and other security measures (previously referenced in the removed repository).
128+
129+
- Unauthorized distribution or reproduction of portions of the official application source (previously observed under SCHALE.Common/FlatData and SCHALE.Common/Crypto in the removed repo). Example (deleted):
130+
[private] (deleted)
131+
[private] (deleted)
132+
133+
These actions not only constitute unauthorized use of NEXON [private]'s intellectual property but also breach the Digital Millennium Copyright Act (DMCA) as they involve circumventing NEXON [private]'s software protection mechanisms.
134+
135+
**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:**
136+
137+
**Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository.**
138+
139+
**Is the work licensed under an open source license?**
140+
141+
No
142+
143+
**What would be the best solution for the alleged infringement?**
144+
145+
Reported content must be removed
146+
147+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
148+
149+
No.
150+
151+
**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.**
152+
153+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
154+
155+
**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.**
156+
157+
**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>.**
158+
159+
**So that we can get back to you, please provide either your telephone number or physical address.**
160+
161+
[private]
162+
163+
**Please type your full name for your signature.**
164+
165+
[private]

0 commit comments

Comments
 (0)