Skip to content

Commit d7e1c0e

Browse files
Merge pull request #17734 from github/updates
Added 2025/05/2025-05-20-spribe.md
2 parents 17466b0 + 542c2d5 commit d7e1c0e

File tree

1 file changed

+106
-0
lines changed

1 file changed

+106
-0
lines changed

2025/05/2025-05-20-spribe.md

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,106 @@
1+
**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.**
2+
3+
Yes, I am authorized to act on the copyright owner's behalf.
4+
5+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
6+
7+
No
8+
9+
**Does your claim involve content on GitHub or npm.js?**
10+
11+
GitHub
12+
13+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
14+
15+
Dear GitHub Trust & Safety Team,
16+
17+
I am writing on behalf of Spribe, a licensed software and gaming provider, to formally report an attempted extortion incident involving threats to publish unauthorized and potentially stolen data on GitHub.
18+
19+
Incident Summary:
20+
An individual identifying as [private] ([private] profile: [private], [private]: [private]) contacted our [private] via [private] and other platforms with the following threats:
21+
22+
Threats to leak source code, databases, and internal tools on GitHub. ([private])
23+
24+
Offers to "verify" stolen data by sending dumps.
25+
26+
Demands for a “good contract” and “small goodwill” payment in exchange for silence.
27+
28+
These threats constitute an extortion attempt and suggest that GitHub may be used as a platform to host or distribute stolen content — including potential database dumps, proxies, or code related to our intellectual property.
29+
30+
Requested Action:
31+
We respectfully request the following:
32+
33+
block any repositories created by or associated with the following aliases:
34+
35+
Username: [private]
36+
37+
Any usage of “Spribe”, “Aviator”, “Spribe Games API”, etc.
38+
39+
Flag and remove any existing or future repositories containing:
40+
41+
Spribe proprietary source code
42+
43+
Production or staging data related to Spribe platforms
44+
45+
Demo-game proxies or reverse-engineered assets
46+
47+
Notify us immediately if any content matching these criteria is published or if access logs indicate unauthorized uploads.
48+
49+
We are prepared to provide legal confirmation and identification if required. We take this matter seriously and are conducting a full security investigation.
50+
51+
Thank you for your attention and cooperation. Please let us know if you require further details or an official legal request.
52+
53+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**
54+
55+
He steal our game code and add it to public repos
56+
57+
**If the original work referenced above is available online, please provide a URL.**
58+
59+
https://spribe.co/games
60+
61+
**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.**
62+
63+
**Based on the above, I confirm that:**
64+
65+
The entire repository is infringing
66+
67+
**Identify the full repository URL that is infringing:**
68+
69+
[invalid]
70+
https://github.com/vampire1991-O/spribe-proxy
71+
72+
**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.**
73+
74+
No
75+
76+
**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:**
77+
78+
**Is the work licensed under an open source license?**
79+
80+
No
81+
82+
**What would be the best solution for the alleged infringement?**
83+
84+
Reported content must be removed
85+
86+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
87+
88+
[private]
89+
[private]
90+
https://github.com/vampire1991-O
91+
92+
**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.**
93+
94+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
95+
96+
**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.**
97+
98+
**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>.**
99+
100+
**So that we can get back to you, please provide either your telephone number or physical address.**
101+
102+
[private]
103+
104+
**Please type your full name for your signature.**
105+
106+
[private]

0 commit comments

Comments
 (0)