Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: updated username due to malicious username spoofing #27729

Open
wants to merge 1 commit into
base: testnet3
Choose a base branch
from

Conversation

Gakunt
Copy link

@Gakunt Gakunt commented Feb 29, 2024

I'm a victim of username spoofing. I've changed username last month, and realized it was my old username that was part of the contributors list. Sadly, I cannot edit it back since a new user has seen taken that username.

The same thing happened for Starknet. Some people with automated software scan for all the currently unused usernames that are part of the contirbutor list.

This is the profile of the current GakiBash, my old username. Account created 6 hours ago, probably automated by some guy that did the same for every other username. : https://github.com/GakiBash

He cannot be part of the contributors list obviously, since he is a new user with no commit.

Capture d’écran 2024-02-29 à 17 35 20

Here are the proofs I am the rightful contributor :

If you use the current contributor link to GakiBash's contribution's, GitHub automatically links it back to me : https://github.com/GakiBash/Aleo-Tiktacto

Here is the opened issue for that contribution : #20554

All this PR does it replacing the 4 mentions of the username "GakiBash" in CONTRIBUTORS.md to "Gakunt" my current username.

Also, I understand every single person opening a PR for such username spoofing might be spam and unmanageable for you. That's why I'm offering to work on username spoofing detection as a global scale in another PR to detect this kind of malicious attack.

Although the username change was a mistake on my end, I believe having malicious people collecting hundreds of badges using such methods are something we should avoid for the project's best interest/

Copy link

codecov bot commented Mar 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.50%. Comparing base (d7fecb3) to head (85b1fe6).
Report is 21 commits behind head on testnet3.

Additional details and impacted files
@@             Coverage Diff              @@
##           testnet3   #27729      +/-   ##
============================================
- Coverage     75.65%   75.50%   -0.16%     
============================================
  Files           203      203              
  Lines          7049     7062      +13     
  Branches       7049     7062      +13     
============================================
- Hits           5333     5332       -1     
- Misses         1716     1730      +14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant