Security Basics

{TITLE}

By Sarah Mitchell, Cybersecurity Educator โ€” 3 June 2026 ยท 6 min read
๐Ÿ” What Happened โ€” Plain English: On June 3, 2026, a security researcher showed how hackers can steal GitHub login tokens just by getting developers to click a link in their web browser. This isn't a virus or a password crack โ€” it's a clever trick that takes advantage of how VS Code handles website connections. Even if you're not a developer, this matters because the tools your friends, family, and favorite apps rely on could be affected.

What Is a "Zero-Day" and Why Should I Care?

A zero-day is a security flaw that the software company doesn't know about and hasn't fixed yet. The name means developers have "zero days" to prepare a fix before attackers can exploit it.

Think of it like discovering a hidden door in your house that you didn't know existed โ€” and someone else already knows where it is. Until you can lock that door (install a patch), your home is vulnerable.

In this case, the hidden door is in VS Code, a free code editor made by Microsoft that millions of developers use every day. The flaw lets attackers steal GitHub tokens โ€” think of tokens as digital keys that let software programs access your online accounts automatically.

A Simple Guide to Tokens vs Passwords

If you've ever used a "Sign in with Google" button, you've used a token. Tokens are different from passwords in important ways:

FeaturePasswordToken
What it isA secret word you typeA digital code your computer sends
Who uses itYou (a human)Software programs
What happens if stolenYou can change your passwordHarder to detect โ€” programs don't "notice" they're stolen
ExpiresNever (unless you change it)Usually lasts hours or days
Access levelOne accountCan have wide access to everything

Key point: The GitHub tokens stolen in this zero-day attack have full access to all the code repositories the developer can access โ€” not just the one they were editing. That's a much bigger problem than a stolen password, which would only let someone log into one account.

What Makes This Vulnerability Different?

Most security bugs we hear about involve hackers finding a weak password or tricking someone into downloading malware. This one is different:

How It Actually Works (Simple Explanation)

  1. You click a GitHub link. When a developer clicks a link to view code on github.dev, their browser sends an OAuth token to prove who they are.
  2. The token has superpowers. This token can access every repository the developer can access, including private ones.
  3. A hidden program hijacks the token. The exploit runs hidden JavaScript that simulates keypresses and installs a fake extension that silently sends the token to the attacker.
  4. The attacker has full access. Now the attacker can download all code, read secrets, and even push malicious code as if they were the legitimate developer.

Think of it like this: you hand your house key to a doorman at a building you're visiting. The doorman is supposed to only use the key for you. But instead, he makes a copy and gives it to a stranger who can now enter your house whenever they want โ€” and you don't even know a copy exists.

Who Is at Risk?

This vulnerability affects anyone who uses github.dev โ€” the browser-based version of VS Code. According to data from GitHub, that's potentially millions of developers worldwide. Even if you're not a developer, you should care because the Miasma supply chain attack disclosed this week (June 1, 2026) showed how attackers can use a single stolen developer credential to infect software packages used by millions. When you need a password immediately, the Instant Password Generator quick tool generates one with zero load time.

What You Can Do Right Now (Even as a Beginner)

  1. Clear browser cookies for github.dev. Open browser Settings โ†’ Cookies and site data โ†’ search for "github.dev" โ†’ Clear data.
  2. Check your GitHub tokens. GitHub.com โ†’ Settings โ†’ Developer Settings โ†’ Personal Access Tokens. Revoke any you don't recognize.
  3. Enable two-factor authentication (2FA). Use an authenticator app, not SMS.
  4. Use different passwords for every account. Start using a password generator to create strong, unique passwords.
  5. Stay informed. Follow security news and act quickly when urgent patches are announced.

Frequently Asked Questions

What is VS Code and do I use it?

VS Code (Visual Studio Code) is a free code editor made by Microsoft. If you're not a developer, you probably don't use it โ€” but the developers who build the apps you use every day definitely do.

Does this affect regular (non-developer) users?

Not directly. However, if a developer you work with is compromised, and they have access to code that powers an app you use, that app could be affected indirectly through a supply chain attack.

How is a token different from a password?

A password is something you type yourself. A token is a digital code that your computer sends automatically. The problem with stolen tokens is that you might not realize they've been taken.

Is Microsoft going to fix this?

Microsoft has not yet commented or released a patch. The researcher chose public disclosure citing a previous bad experience with Microsoft's security team. In the meantime, clear github.dev cookies as a temporary measure.

What's the single most important thing I can do?

If you're a developer: clear your github.dev cookies right now. If you're not: help the developers in your life understand this risk. Use strong, unique passwords everywhere and enable 2FA.

๐Ÿ” Generate a Strong Password Now

Affiliate Disclosure: This post may contain affiliate links. If you purchase through these links, we may earn a small commission at no extra cost to you. FreeStrongPassword.com is free to use. Full disclosure.

โญ Make us your preferred source on Google