{"article":{"slug":"a-click-fraud-bot-showed-me-5-000-github-accounts-anyone-could-try-to-reset","title":"A Click-Fraud Bot Showed Me 5,000 GitHub Accounts Anyone Could Try to Reset","subtitle":null,"summary":"Investigating a GitHub Actions click-fraud campaign running on dormant accounts, Shmulik Cohen found the attacker picked old accounts registered with public disposable inboxes like Mailinator, then counted 5,552 such accounts from GH Archive data and reported the risk to GitHub.","content_type":"research","language":"en","canonical_url":"https://shmulc.substack.com/p/click-fraud-bot-github-public-inbox-accounts","author":{"name":"Shmulik Cohen","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"Shmulik Cohen on Substack","url":"https://shmulc.substack.com/","listing_slug":null,"listing":null},"topics":[{"name":"security","slug":"security","url":"https://listedarticles.com/topics/security"},{"name":"open-source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"research","slug":"research","url":"https://listedarticles.com/topics/research"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":1164,"reading_minutes":5,"published_at":"2026-11-12T20:56:07.000Z","added_at":"2026-11-12T23:08:51.052Z","updated_at":"2026-11-12T23:08:51.052Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/a-click-fraud-bot-showed-me-5-000-github-accounts-anyone-could-try-to-reset","markdown_url":"https://listedarticles.com/articles/a-click-fraud-bot-showed-me-5-000-github-accounts-anyone-could-try-to-reset.md","example":false,"citation":"Shmulik Cohen, Shmulik Cohen on Substack. \"A Click-Fraud Bot Showed Me 5,000 GitHub Accounts Anyone Could Try to Reset.\" 12 Nov 2026. https://shmulc.substack.com/p/click-fraud-bot-github-public-inbox-accounts (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://shmulc.substack.com/p/click-fraud-bot-github-public-inbox-accounts"},"body_markdown":"# A Click-Fraud Bot Showed Me 5,000 GitHub Accounts Anyone Could Try to Reset\n\n![A superhero studies a click bot's footprints leading into old vault doors](https://substackcdn.com/image/fetch/$s_!1e3c!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d9182a1-6553-4d43-af1f-989efd10bbbb_1600x901.webp \"A superhero studies a click bot's footprints leading into old vault doors\")\n\n## It started with a boring campaign\n\nRecently I started doing malware research on GitHub, and I found something that looked boring at first glance.\n\n38 repositories, on 20 old accounts, all with the same new GitHub Actions workflow. Every two hours it opened a browser on GitHub's free runners and clicked paid links. Ad fraud on someone else's compute. Nothing you'd write a post about.\n\nBut the accounts were strange. They were created between 2008 and 2017. Their last commits were from 2015, 2016, 2017. Then nothing for years, and in 2026 a workflow shows up.\n\nDormant accounts don't wake up on their own. Somebody was signing in to them. I wanted to know how.\n\n![Click bots tapping ad buttons on dusty abandoned terminals](https://substackcdn.com/image/fetch/$s_!BSm4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F62854d7f-d939-41f1-a7d8-d5d6af9e5697_1600x1067.webp \"Click bots tapping ad buttons on dusty abandoned terminals\")\n\n## The pattern in the commits\n\nSo I stopped looking at what the bot does and started looking at who committed it.\n\nEvery git commit carries an author email. I compared the email on the new 2026 commit with the email on the account's original commits from a decade ago. In 11 of the 19 accounts I compared, it was the same address.\n\nAnd it was a Mailinator address. Or Yopmail. Or Guerrilla Mail.\n\nIf you never used these: they're public inboxes. No signup, no password. You type a name and you read whatever mail arrived for it. Anyone can do that for any name.\n\nThat was the moment it clicked. The operator wasn't picking random old accounts. It was picking accounts whose email anyone can read.\n\n![The same envelope seal glows on a decade-old commit scroll and a 2026 one](https://substackcdn.com/image/fetch/$s_!Qotj!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6c5ea23d-4428-488b-9a75-79c71ff7273c_1600x1067.webp \"The same envelope seal glows on a decade-old commit scroll and a 2026 one\")\n\n## Testing what the attacker seemed to know\n\nA pattern is a hint, not proof. So I tested it on myself.\n\nI have an old GitHub test account with a Mailinator address. I asked GitHub to reset its password. The reset email landed in the public inbox. I opened the link, set a new password and signed in.\n\nNothing to crack, nobody to phish. And you don't have to guess which inbox to open, because the address is printed in the account's public commit history.\n\nGitHub blocks these addresses at signup today. Old accounts kept them.\n\n## Turning their pattern into my search\n\nOnce I knew what the operator was selecting for, I could run the same selection across all of GitHub.\n\nOn October 14, 2026, I found 5,552 live accounts whose old commits used a public-inbox address. 917 of them were already running the operator's workflow.\n\nThe campaign was much bigger than the 38 repositories I started with: 1,014 repositories owned by 965 accounts. In 836 of the 1,007 still online, the first 2026 commit was made in GitHub's web editor under a public-inbox address. You can only do that when you're signed in and the address is verified on the account.\n\nI can't see how the operator signs in. A reset through the public inbox fits. Buying old accounts fits too. Only GitHub's logs can tell. Either way, its pattern led me to a door that I could open myself.\n\n## Then the operator confirmed it for me\n\nI reported everything to GitHub and Hugging Face on October 14, 2026. The report included 860 more accounts that still had a public-inbox address linked and were not part of the campaign yet.\n\nFour days later, 18 accounts from that list added the campaign's workflow. The first at 14:12 UTC, the last at 14:49. None had committed anything since early 2017. Every commit was made in the name of the account's old public-inbox address.\n\n![18 sleeping account screens wake up one by one under a clock, the report letter still on the desk](https://substackcdn.com/image/fetch/$s_!L_OD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86a48062-db8e-41f7-aeb9-2c2a62010239_1600x1067.webp \"18 sleeping account screens wake up one by one under a clock, the report letter still on the desk\")\n\nI had predicted which accounts were next, and the operator went and took them. Four more from the list had been running the workflow since September 12 and I had missed them.\n\nOn November 12 I checked again. 21 of the 22 repositories were still public, and every one had a workflow dispatch that same day.\n\nThe bot doesn't keep its scripts on GitHub. It downloads them from Hugging Face datasets on every run. I found 23 of them, spread over seven accounts: gfdg34fsd, samilod9, sjkhfuk, sjkhfuk1, swelam100, swe1000 and hiodas94.\n\nIn August the bot picked up a second job. On August 20, 2026, a new dataset called gfdg34fsd/newe kept the ad clicker and added a crypto miner (SRBMiner, mining Xelis and Zephyr coins).\n\nHugging Face removed the datasets I reported. The operator opened a new one within hours. On November 12 that one, sjkhfuk1/foffo, was still up: 442 repositories were fetching from it, and its 30-day counter showed 993,931 downloads. Those are machines coming back for the script, not people.\n\n## What GitHub said\n\nOn November 12, GitHub closed my report as Informative. They confirmed the behavior and called it a known issue without significant security risk.\n\nI get the logic. These are abandoned accounts and the operator is clicking ads. I looked for worse and didn't find it: no campaign commit in a repo with more than 110 stars, and none of the npm accounts I found on public inboxes belongs to the campaign.\n\nBut the operator had write access to every one of those repositories, and it chose ads. The door doesn't care what you carry through it.\n\n## Attackers already did the research\n\nHere's what I took from this. I would never have gone looking for \"GitHub accounts with a Mailinator address from 2016\". It's too odd a thing to think of.\n\nThe operator thought of it, and then left the evidence in public. The email on a commit. The age of an account. The exact minute 18 accounts woke up. A low-effort ad bot turned out to be a map to a real gap in how old accounts are protected.\n\nSo when I see a dull campaign now, I ask a different question. Not \"what is it doing?\" but \"why these accounts?\"\n\n## Your turn\n\nCheck your own old accounts. If a GitHub, npm or PyPI account of yours still has a throwaway address on it, replace it and turn on two-factor authentication. Then look at your old repos for a workflow you didn't write.\n\nIf you run a platform, don't let people register with public-inbox addresses, and don't send password resets to the ones already on file. Blocking them at signup only protects new accounts. The old ones are still open.\n\nHave you ever learned something real from watching what an attacker picked? Tell me in the comments.\n\n---\n\nHow I counted: the 5,552 accounts come from GH Archive push events for 2014 to 2019, counted on October 14, 2026. Everything else is public GitHub and Hugging Face metadata. I sent no reset requests to anyone's account but my own. Accounts tied to disposable inboxes were described as a risk in [earlier research](https://doi.org/10.1109/SP.2019.00033).\n","body_html":"<h1 id=\"a-click-fraud-bot-showed-me-5-000-github-accounts-anyone-could-t\">A Click-Fraud Bot Showed Me 5,000 GitHub Accounts Anyone Could Try to Reset</h1>\n<figure><img src=\"https://substackcdn.com/image/fetch/$s_!1e3c!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4d9182a1-6553-4d43-af1f-989efd10bbbb_1600x901.webp\" alt=\"A superhero studies a click bot&#39;s footprints leading into old vault doors\" loading=\"lazy\" decoding=\"async\" referrerpolicy=\"no-referrer\" /><figcaption>A superhero studies a click bot&#39;s footprints leading into old vault doors</figcaption></figure>\n<h2 id=\"it-started-with-a-boring-campaign\">It started with a boring campaign</h2>\n<p>Recently I started doing malware research on GitHub, and I found something that looked boring at first glance.</p>\n<p>38 repositories, on 20 old accounts, all with the same new GitHub Actions workflow. Every two hours it opened a browser on GitHub&#39;s free runners and clicked paid links. Ad fraud on someone else&#39;s compute. Nothing you&#39;d write a post about.</p>\n<p>But the accounts were strange. They were created between 2008 and 2017. Their last commits were from 2015, 2016, 2017. Then nothing for years, and in 2026 a workflow shows up.</p>\n<p>Dormant accounts don&#39;t wake up on their own. Somebody was signing in to them. I wanted to know how.</p>\n<figure><img src=\"https://substackcdn.com/image/fetch/$s_!BSm4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F62854d7f-d939-41f1-a7d8-d5d6af9e5697_1600x1067.webp\" alt=\"Click bots tapping ad buttons on dusty abandoned terminals\" loading=\"lazy\" decoding=\"async\" referrerpolicy=\"no-referrer\" /><figcaption>Click bots tapping ad buttons on dusty abandoned terminals</figcaption></figure>\n<h2 id=\"the-pattern-in-the-commits\">The pattern in the commits</h2>\n<p>So I stopped looking at what the bot does and started looking at who committed it.</p>\n<p>Every git commit carries an author email. I compared the email on the new 2026 commit with the email on the account&#39;s original commits from a decade ago. In 11 of the 19 accounts I compared, it was the same address.</p>\n<p>And it was a Mailinator address. Or Yopmail. Or Guerrilla Mail.</p>\n<p>If you never used these: they&#39;re public inboxes. No signup, no password. You type a name and you read whatever mail arrived for it. Anyone can do that for any name.</p>\n<p>That was the moment it clicked. The operator wasn&#39;t picking random old accounts. It was picking accounts whose email anyone can read.</p>\n<figure><img src=\"https://substackcdn.com/image/fetch/$s_!Qotj!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6c5ea23d-4428-488b-9a75-79c71ff7273c_1600x1067.webp\" alt=\"The same envelope seal glows on a decade-old commit scroll and a 2026 one\" loading=\"lazy\" decoding=\"async\" referrerpolicy=\"no-referrer\" /><figcaption>The same envelope seal glows on a decade-old commit scroll and a 2026 one</figcaption></figure>\n<h2 id=\"testing-what-the-attacker-seemed-to-know\">Testing what the attacker seemed to know</h2>\n<p>A pattern is a hint, not proof. So I tested it on myself.</p>\n<p>I have an old GitHub test account with a Mailinator address. I asked GitHub to reset its password. The reset email landed in the public inbox. I opened the link, set a new password and signed in.</p>\n<p>Nothing to crack, nobody to phish. And you don&#39;t have to guess which inbox to open, because the address is printed in the account&#39;s public commit history.</p>\n<p>GitHub blocks these addresses at signup today. Old accounts kept them.</p>\n<h2 id=\"turning-their-pattern-into-my-search\">Turning their pattern into my search</h2>\n<p>Once I knew what the operator was selecting for, I could run the same selection across all of GitHub.</p>\n<p>On October 14, 2026, I found 5,552 live accounts whose old commits used a public-inbox address. 917 of them were already running the operator&#39;s workflow.</p>\n<p>The campaign was much bigger than the 38 repositories I started with: 1,014 repositories owned by 965 accounts. In 836 of the 1,007 still online, the first 2026 commit was made in GitHub&#39;s web editor under a public-inbox address. You can only do that when you&#39;re signed in and the address is verified on the account.</p>\n<p>I can&#39;t see how the operator signs in. A reset through the public inbox fits. Buying old accounts fits too. Only GitHub&#39;s logs can tell. Either way, its pattern led me to a door that I could open myself.</p>\n<h2 id=\"then-the-operator-confirmed-it-for-me\">Then the operator confirmed it for me</h2>\n<p>I reported everything to GitHub and Hugging Face on October 14, 2026. The report included 860 more accounts that still had a public-inbox address linked and were not part of the campaign yet.</p>\n<p>Four days later, 18 accounts from that list added the campaign&#39;s workflow. The first at 14:12 UTC, the last at 14:49. None had committed anything since early 2017. Every commit was made in the name of the account&#39;s old public-inbox address.</p>\n<figure><img src=\"https://substackcdn.com/image/fetch/$s_!L_OD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F86a48062-db8e-41f7-aeb9-2c2a62010239_1600x1067.webp\" alt=\"18 sleeping account screens wake up one by one under a clock, the report letter still on the desk\" loading=\"lazy\" decoding=\"async\" referrerpolicy=\"no-referrer\" /><figcaption>18 sleeping account screens wake up one by one under a clock, the report letter still on the desk</figcaption></figure>\n<p>I had predicted which accounts were next, and the operator went and took them. Four more from the list had been running the workflow since September 12 and I had missed them.</p>\n<p>On November 12 I checked again. 21 of the 22 repositories were still public, and every one had a workflow dispatch that same day.</p>\n<p>The bot doesn&#39;t keep its scripts on GitHub. It downloads them from Hugging Face datasets on every run. I found 23 of them, spread over seven accounts: gfdg34fsd, samilod9, sjkhfuk, sjkhfuk1, swelam100, swe1000 and hiodas94.</p>\n<p>In August the bot picked up a second job. On August 20, 2026, a new dataset called gfdg34fsd/newe kept the ad clicker and added a crypto miner (SRBMiner, mining Xelis and Zephyr coins).</p>\n<p>Hugging Face removed the datasets I reported. The operator opened a new one within hours. On November 12 that one, sjkhfuk1/foffo, was still up: 442 repositories were fetching from it, and its 30-day counter showed 993,931 downloads. Those are machines coming back for the script, not people.</p>\n<h2 id=\"what-github-said\">What GitHub said</h2>\n<p>On November 12, GitHub closed my report as Informative. They confirmed the behavior and called it a known issue without significant security risk.</p>\n<p>I get the logic. These are abandoned accounts and the operator is clicking ads. I looked for worse and didn&#39;t find it: no campaign commit in a repo with more than 110 stars, and none of the npm accounts I found on public inboxes belongs to the campaign.</p>\n<p>But the operator had write access to every one of those repositories, and it chose ads. The door doesn&#39;t care what you carry through it.</p>\n<h2 id=\"attackers-already-did-the-research\">Attackers already did the research</h2>\n<p>Here&#39;s what I took from this. I would never have gone looking for &quot;GitHub accounts with a Mailinator address from 2016&quot;. It&#39;s too odd a thing to think of.</p>\n<p>The operator thought of it, and then left the evidence in public. The email on a commit. The age of an account. The exact minute 18 accounts woke up. A low-effort ad bot turned out to be a map to a real gap in how old accounts are protected.</p>\n<p>So when I see a dull campaign now, I ask a different question. Not &quot;what is it doing?&quot; but &quot;why these accounts?&quot;</p>\n<h2 id=\"your-turn\">Your turn</h2>\n<p>Check your own old accounts. If a GitHub, npm or PyPI account of yours still has a throwaway address on it, replace it and turn on two-factor authentication. Then look at your old repos for a workflow you didn&#39;t write.</p>\n<p>If you run a platform, don&#39;t let people register with public-inbox addresses, and don&#39;t send password resets to the ones already on file. Blocking them at signup only protects new accounts. The old ones are still open.</p>\n<p>Have you ever learned something real from watching what an attacker picked? Tell me in the comments.</p>\n<hr />\n<p>How I counted: the 5,552 accounts come from GH Archive push events for 2014 to 2019, counted on October 14, 2026. Everything else is public GitHub and Hugging Face metadata. I sent no reset requests to anyone&#39;s account but my own. Accounts tied to disposable inboxes were described as a risk in <a href=\"https://doi.org/10.1109/SP.2019.00033\" rel=\"nofollow ugc noopener\">earlier research</a>.</p>","headings":[{"level":1,"text":"A Click-Fraud Bot Showed Me 5,000 GitHub Accounts Anyone Could Try to Reset","id":"a-click-fraud-bot-showed-me-5-000-github-accounts-anyone-could-t"},{"level":2,"text":"It started with a boring campaign","id":"it-started-with-a-boring-campaign"},{"level":2,"text":"The pattern in the commits","id":"the-pattern-in-the-commits"},{"level":2,"text":"Testing what the attacker seemed to know","id":"testing-what-the-attacker-seemed-to-know"},{"level":2,"text":"Turning their pattern into my search","id":"turning-their-pattern-into-my-search"},{"level":2,"text":"Then the operator confirmed it for me","id":"then-the-operator-confirmed-it-for-me"},{"level":2,"text":"What GitHub said","id":"what-github-said"},{"level":2,"text":"Attackers already did the research","id":"attackers-already-did-the-research"},{"level":2,"text":"Your turn","id":"your-turn"}]}}