Scam repo

[pawamoy]

https://github.com/LidoRewardPromo/Lido-Staking

Check the issues. They're tagging lots of people.

[MHuiG]

Some people are currently conducting spamming and phishing activities.

This user or bot has been sending a large amount of spam using the @ function in issues.

https://github.com/kamino-network/kamino-finance/issues

https://github.com/lido-community/lido/issues

https://github.com/kamino-staking/kamino-staking-pool/issues

https://github.com/LidoFiStaking/Lido-Staking/issues

Don't click on unknown links. It's a scam.

https://github.com/orgs/community/discussions/75571#discussioncomment-14466344

https://github.com/orgs/community/discussions/174223

https://github.com/orgs/community/discussions/174380

Bug: ghost notifications

https://github.com/orgs/community/discussions/6874#discussioncomment-2859125

[shomilsaini]

Same for this - https://github.com/gitcoinoda/org/
Just got the scam & Spam email. Twice in a day.
Other one was - https://github.com/outcaster552/gitcoinpromosender/ which was promptly block i assume.

Thanks

[shaneholloman]

I can't remove this from my notifications inbox. It appears empty, but this company still remains.

[Xdy1579883916]

To delete (mark done) in nodejs:

https://github.com/Xdy1579883916/github_notifications_fix/blob/master/index.ts

[liesauer]

is there a web script version of this? i mean i already logged on GitHub, and i don't want to create a api token just for removing this stupid notifaction

[ElijahLynn]

Same. GitHub, you gotta do something about this in the UI:

[gokaygurcan]

@ElijahLynn here: https://x.com/gokaygurcan/status/1897061925634367614

[ElijahLynn]

thanks!

for those who cancelled X

https://xcancel.com/gokaygurcan/status/1897061925634367614

[rrozek]

Got tagged as well -_-

[shigeya]

I can't remove this from my notifications inbox. It appears empty, but this company still remains.

This is happening to me, and this makes the GitHub inbox unread mark super useless :<

[jxu]

I wish github would fix this notification issue. They probably didn't test their unread indicator for deleted repos.

[B-3000]

@sambavelnati @polverarijv Unfortunately, this is a known bug in GitHub notifications and hopefully they'll solve it soon.

But in the meantime, here are some of the solutions found in other thread discussions regarding this -

1. https://github.com/orgs/community/discussions/6874#discussioncomment-1775744
2. https://github.com/orgs/community/discussions/6874#discussioncomment-14507162
3. https://gist.github.com/Nriver/42feddd2a369a8f1519b47adb81ebef8
4. https://github.com/emmanuel-ferdman/gh-gonest
5. https://gist.github.com/jeremystretch/2c09f76837fc5af787fe9ff7747ecf3f
6. https://github.com/orgs/community/discussions/174310#discussioncomment-14474599
7. https://github.com/orgs/community/discussions/6874#discussioncomment-14481926
8. https://gist.github.com/eseiler/d3a6f978ceea1853f0c558879cf859c1

[ShalokShalom]

Another scam repo: notification-mail/gitcoin.com#56

[ShalokShalom]

I am sure they count it as such.

[Tama10]

Found another.

gitcoinnotifypromo/gitcoincodao

EDIT: yet another: gitcoinod/org

[jxu]

The scambots are going crazy today

[sgpublic]

Now another one: gitcoinod/org

[thliang01]

repo: https://github.com/gitcoinod/org/issues

[shomilsaini]

Same for this - https://github.com/gitcoinoda/org/
Just got the scam & Spam email. Twice in a day.
Other one was - https://github.com/outcaster552/gitcoinpromosender/ which was promptly block i assume.

Thanks

[shuvashish76]

gitcoinoda/org#395

@asdeennermosephad2 nice you deleted the repo and issue but here is the archive link https://archive.is/3dpRu

[sambavelnati]

I could not clear this message. Something is wrong when the repos are not known and someone is able to modify notifications to all GitHub Users in some way.

[bamjun]

https://github.com/orgs/community/discussions/174283#discussioncomment-14527039

try this

uvx fown auth login

uvx fown noti delete -r

or

uvx fown noti delete gitcoinod/org -r

[porkmanager]

Also got these 2 in last two days, and cant remove it.

Edit. Removed. Select all notifications > mark as Done.

[pawamoy]

@github yet another https://github.com/ycommbinator/-co. Can't report from the mobile app

[spbmnn]

Can't report the repo and/or issues from the mobile site either.

[jxu]

I opened a github issue ticket and got a reply saying the issue is being investigated.

Suggestion: disable mass tagging, at least for unverified users. Disable unverified users from being able to tag and generate a notification email by default.

[ayrudev]

Same over here, GitHub needs a mark all as read for this reason

[shomilsaini]

Got another notification now - https://github.com/paradigm-ventures/paradigm/

[JonathanHuot]

same scam with
paradigmmm/paradigm-stack#288

[dubstard]

also good to keep an eye on https://github.com/paradigmm/

[jxu]

Until it's fixed I'm using uBlock to hide the inbox icon completely.
The filter is

github.com##.AppHeader-globalBar-end > .js-socket-channel

[Tama10]

Huh, thanks, bro. Unlike other methods, this one worked.

[qodeninja]

Thank goodness I was not the only one having this issue ugh. This worked for me > https://github.com/orgs/community/discussions/174310#discussioncomment-14514685

[MisutaaAsriel]

I was able to remove the notification using the terminal, but this only works for those with access to a machine with the github CLI application.

What is worse: You still show as subscribed to the repo in the sidebar. In my case, paradigmmm/paradigm-stack. And I cannot remove it using the API because it doesn't exist.

[bamjun]

https://github.com/orgs/community/discussions/174283#discussioncomment-14527039

try this

uvx fown auth login

uvx fown noti delete -r

or

uvx fown noti delete paradigmmm/paradigm-stack -r

[MisutaaAsriel]

@bamjun I appreciate the attempt to help but uh:

1. I am on Mac, and this uvx is neither part of the GitHub CLI nor available via Homebrew. I don't feel like futzing with third party scripts and packages just to do a simple task.
2. If removing a repository (not just the notification) cannot be done with the standard REST API and the GitHub CLI, that's still an issue.
3. This shouldn't be an issue at all, still.

[ElijahLynn]

I encourage people to keep posting the same repos here. Why? Because people who might be searching for the string of the repo plus GitHub notification spam, might more easily end up here and find comfort knowing it isn't just happening to them AND finding work arounds until GitHub fixes this issue.

[ayrudev]

ycommbinator/-co was one of them I received

[RYANAIR5719]

Hmm... did you file a formal complaint like this?

[RYANAIR5719]

@pawamoy

[pawamoy]

No: I mostly get the scam notif on the mobile app, from where I can't report. I won't login from my mobile web browser. By the time I'm at the desktop, GitHub removed the repo anyway.

[eeston]

Another one...

paradigm-hub/paradigm

[alex2276564]

Fix Ghost GitHub Notifications (Browser Console Method)

⚠️Warning - after this, all your unread notifications will be considered read.

The Problem

Your GitHub notifications tab shows a blue badge, but when you open it — nothing is there. This happens when repositories are deleted but their notification mentions remain.

Solution (5 minutes)

Step 1: Create a Personal Access Token

1. Go to https://github.com/settings/tokens/new
2. Note: Clear ghost notifications (any name)
3. Expiration: 7 days (you'll delete it after)
4. Permissions: Check only notifications ✅
5. Click "Generate token" (green button at bottom)
6. Copy the token (starts with ghp_...) — you won't see it again!

Step 2: Open Browser Console

1. Open https://github.com/notifications
2. Press F12 (or Right-click → Inspect)
3. Click the "Console" tab at the top
4. You'll see a command prompt >

Step 3: Run the Script

1. Copy this code:

const TOKEN = 'ghp_YOUR_TOKEN_HERE'; // Replace with your token!

fetch('https://api.github.com/notifications', {
  headers: {
    'Authorization': `token ${TOKEN}`,
    'X-GitHub-Api-Version': '2022-11-28'
  }
})
.then(r => r.json())
.then(async notifications => {
  console.log(`Found ${notifications.length} notifications`);
  
  for (let n of notifications) {
    console.log(`Clearing: ${n.subject.title}`);
    await fetch(`https://api.github.com/notifications/threads/${n.id}`, {
      method: 'PATCH',
      headers: {
        'Authorization': `token ${TOKEN}`,
        'X-GitHub-Api-Version': '2022-11-28'
      }
    });
  }
  
  console.log('✅ Done! Refresh the page');
});

2. Replace ghp_YOUR_TOKEN_HERE with your actual token
3. Paste into the Console
4. Press Enter

Step 4: Wait & Refresh

• You'll see: Found X notifications → Clearing: ... → ✅ Done!
• Refresh the page (Ctrl+R / Cmd+R)
• Blue badge should be gone! 🎉

Step 5: Delete the Token (Important!)

1. Go to https://github.com/settings/tokens
2. Find your token → Click Delete
3. Done — token can't be misused now

---

Troubleshooting

"401 Unauthorized" → Token is wrong, create a new one
"403 Forbidden" → You didn't enable notifications permission
Still see badge? → Hard refresh: Ctrl+Shift+R (Cmd+Shift+R on Mac)

---

Why this works: The script marks ghost notifications as "read" via GitHub API, which the web UI can't access for deleted repos.

[pawamoy]

Or install gh, authenticate with gh auth login, get the notification thread ID with gh api notification, and mark it as read with gh api -X DELETE notifications/threads/<ID>. Or just mark all current notifications as read with gh api notifications -X PUT -f last_read_at=$(date -Iminutes) -f read=true.

[jxu]

Never paste something someone gives you into the browser console to run! Especially AI output.

[Rorschach1010]

Fix Ghost GitHub Notifications (Browser Console Method)

⚠️Warning - after this, all your unread notifications will be considered read.

The Problem

Your GitHub notifications tab shows a blue badge, but when you open it — nothing is there. This happens when repositories are deleted but their notification mentions remain.

Solution (5 minutes)

Step 1: Create a Personal Access Token

1. Go to https://github.com/settings/tokens/new

2. **Note**: `Clear ghost notifications` (any name)

3. **Expiration**: 7 days (you'll delete it after)

4. **Permissions**: Check **only** `notifications` ✅

5. Click **"Generate token"** (green button at bottom)

6. **Copy the token** (starts with `ghp_...`) — you won't see it again!

Step 2: Open Browser Console

1. Open https://github.com/notifications

2. Press **F12** (or Right-click → Inspect)

3. Click the **"Console"** tab at the top

4. You'll see a command prompt `>`

Step 3: Run the Script

1. **Copy this code:**

const TOKEN = 'ghp_YOUR_TOKEN_HERE'; // Replace with your token!

fetch('https://api.github.com/notifications', {
  headers: {
    'Authorization': `token ${TOKEN}`,
    'X-GitHub-Api-Version': '2022-11-28'
  }
})
.then(r => r.json())
.then(async notifications => {
  console.log(`Found ${notifications.length} notifications`);
  
  for (let n of notifications) {
    console.log(`Clearing: ${n.subject.title}`);
    await fetch(`https://api.github.com/notifications/threads/${n.id}`, {
      method: 'PATCH',
      headers: {
        'Authorization': `token ${TOKEN}`,
        'X-GitHub-Api-Version': '2022-11-28'
      }
    });
  }
  
  console.log('✅ Done! Refresh the page');
});

2. **Replace** `ghp_YOUR_TOKEN_HERE` with your actual token

3. **Paste** into the Console

4. Press **Enter**

Step 4: Wait & Refresh

* You'll see: `Found X notifications` → `Clearing: ...` → `✅ Done!`

* **Refresh the page** (Ctrl+R / Cmd+R)

* Blue badge should be **gone**! 🎉

Step 5: Delete the Token (Important!)

1. Go to https://github.com/settings/tokens

2. Find your token → Click **Delete**

3. Done — token can't be misused now

Troubleshooting

"401 Unauthorized" → Token is wrong, create a new one "403 Forbidden" → You didn't enable notifications permission Still see badge? → Hard refresh: Ctrl+Shift+R (Cmd+Shift+R on Mac)

Why this works: The script marks ghost notifications as "read" via GitHub API, which the web UI can't access for deleted repos.

Thanks,
while this worked like a charm to remove the blue badge of unread notifications, all 3 repositories are still listed at the bottom left (right above the "Manage notifications" button). Is there a solution for that?

[alexpatukby]

Another Info stealer private repo https://github.com/leadleaper220-sketch/lmngrls

[shinybrightstar]

Hi @pawamoy, 👋🏻 We really appreciate you flagging this. The best route to get this to the proper GitHub team is to use our abuse reporting tools. Here's all the info:

• Reporting abuse or spam
• Reporting a user
• Reporting an issue or pull request
• Reporting a comment

You can report behavior and content that violates community guidelines and terms. We are going to close this post, but for this and any future incidents, please refer to the links above.

Thank you!

[pawamoy]

@eeston See https://github.com/orgs/community/discussions/174228#discussioncomment-14624657 and other comments in the discussion.

[pawamoy]

@shinybrightstar thanks 🙂 Ideally you'd update the mobile app so we can report from there directly.

[eeston]

Thanks @pawamoy I did see that, I was just encouraging them to actually fix the issue 😅

[ElijahLynn]

As long as we all still have unread notifications, but no actual notifications in our GitHub notifications list, then you SHOULD NOT CLOSE THIS DISCUSSION.

In order to close this discussion, GitHub should fix the issue by writing a script at the GH level, that runs on cron, that finds all notifications that don't have a repo attached to them anymore and mark them as read/delete them.

Not everyone wants to clear ALL of their notifications with curl, and it will continue to happen anyways.

[pawamoy]

I reopened this one btw, dating from february: https://github.com/orgs/community/discussions/150670.