Skip to content

Commit d7eaefa

Browse files
Merge pull request #20339 from github/updates
Added 2026/04/2026-04-17-seoul-system.md
2 parents eca53e6 + fe68927 commit d7eaefa

File tree

1 file changed

+86
-0
lines changed

1 file changed

+86
-0
lines changed

2026/04/2026-04-17-seoul-system.md

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
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).
2+
3+
---
4+
5+
**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.**
6+
7+
Yes, I am authorized to act on the copyright owner's behalf.
8+
9+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
10+
11+
No
12+
13+
**Does your claim involve content on GitHub or npm.js?**
14+
15+
GitHub
16+
17+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
18+
19+
I am the [private] [private] of Seoul System Co., Ltd., located in [private], [private]. Our company holds the exclusive copyright to the source code in question. This code was developed internally by our company and is our proprietary property.
20+
The content was unauthorizedly uploaded to GitHub by a freelancer in violation of their contract with us. This occurred during a process in 2021 when parts of this program were being customized and delivered to a client. We have only discovered this unauthorized disclosure today.
21+
Proprietary software source code including internal database configurations. Please Immediate removal of the repository and all associated forks.
22+
23+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
24+
25+
The copyrighted work is the proprietary source code developed and exclusively owned by Seoul System Co., Ltd., located in [private], [private].
26+
This code represents our entire internal Web Content Management Architecture (WCMA) system. It includes, but is not limited to, backend logic, APIs, data interfaces, HTML data, and all related configuration components essential for our web business operations.
27+
While portions of this code were developed by employees and freelancers, all such work was performed under strict agreements that mandate the full transfer of all intellectual property (IP) rights to Seoul System Co., Ltd. Therefore, all intellectual property rights belong solely and exclusively to our company. This source code is strictly managed as confidential and proprietary material and has never been authorized for public disclosure.
28+
Furthermore, this unauthorized disclosure includes highly sensitive internal database credentials and server configurations, posing an immediate and severe security threat to our corporate infrastructure.
29+
I also request the immediate removal of all existing forks of this repository.
30+
31+
**If the original work referenced above is available online, please provide a URL.**
32+
33+
Not publicly available. The original source code is proprietary and maintained internally by the company.
34+
35+
**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.**
36+
37+
**Based on the above, I confirm that:**
38+
39+
The entire repository is infringing
40+
41+
**Identify the full repository URL that is infringing:**
42+
43+
https://github.com/raika11/-
44+
45+
**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.**
46+
47+
Yes
48+
49+
**What technological measures do you have in place and how do they effectively control access to your copyrighted material?**
50+
51+
Access to the copyrighted source code is strictly restricted through secure, private repositories requiring multi-factor authenticated access. Only authorized employees and contractors with specific, granted permissions can access the repository. Access control is enforced through role-based access control (RBAC) and company-managed authentication systems. Furthermore, all access is subject to strict non-disclosure agreements (NDAs), ensuring that the code remains confidential and is not authorized for public disclosure.
52+
53+
**How is the accused project designed to circumvent your technological protection measures?**
54+
55+
The individual did not technically bypass encryption or security measures. However, they had authorized access to the private repository as a contractor for project-related work and misused that access by copying and uploading the proprietary source code to a public repository without authorization.
56+
This resulted in unauthorized disclosure of confidential and proprietary material that was intended to remain restricted under access control policies.
57+
58+
**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:**
59+
60+
**Is the work licensed under an open source license?**
61+
62+
No
63+
64+
**What would be the best solution for the alleged infringement?**
65+
66+
Reported content must be removed
67+
68+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
69+
70+
The provided [private] appears to be inactive or unreachable, and no valid email address is available.
71+
72+
**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.**
73+
74+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
75+
76+
**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.**
77+
78+
**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>.**
79+
80+
**So that we can get back to you, please provide either your telephone number or physical address.**
81+
82+
[private]
83+
84+
**Please type your full name for your signature.**
85+
86+
[private]

0 commit comments

Comments
 (0)