AI summary by TwinMind
Why Microsoft deleted this extension from MILLIONS of computers
Theo - t3․gg
52m 15s
Extension Removal and Background
- VS Code team deleted Material Theme extension from marketplace, uninstalled from millions of devices
- First ever update to "removed packages" section on VS Code Marketplace repo
- Extension removed February 26th for "heavily obfuscated code and unreasonable dependencies including ability for running child processes"
- Material theme surrounded in previous drama, not considered good theme by presenter
- Presenter spent 40+ hours over 4 days investigating situation
- Multiple security experts consulted to understand what was happening
Previous Drama Context
- Mattia (creator) made theme closed source, got angry at others using old open source version
- Started threatening lawsuits against other projects using similar names/colors
- Targeted other editors like Zed and Sublime Text with harassment
- Been doing this behavior for years, previously harassed Sublime Text
- Presenter maintains fork due to this drama, deleted 10,000+ lines of unnecessary code
Technical Issues with Extension
- Theme built with complex generators instead of simple JSON files like other themes
- Has access to spawning processes and reading file system (inappropriate for theme)
- Heavily obfuscated code making it impossible to understand functionality
- Uses dependencies with massive security implications unnecessarily
- Performance impact up to 80% slower due to obfuscation
- All commit history deleted, hundreds of contributors' work erased
Malicious Software Indicators
- Requesting access to things it doesn't need (file system, child processes)
- Dependencies for functionality theme shouldn't require
- Heavy code obfuscation to hide actual functionality
- Pattern matches XZ Utils hack from previous year
- 90%+ likelihood software is malicious when exhibiting all three traits
Creator's Response Post-Removal
- Did not reach out to VS Code team for resolution
- Started complaining everywhere, throwing everyone under bus
- Created conspiracy theories blaming presenter for coordinated attack
- Made over 500 GitHub accounts in 2 days
- Republished extension under 4 different names to circumvent ban
- Edited single GitHub issue 24 times in 10 hours
- Consistently added/removed clown emoji next to presenter's name
Presenter's Investigation and Fork
- Spent night until 5am auditing code, pulling in security experts
- Told VS Code team to take down his fork immediately if malware found
- Removed analytics, changelogs, Open Collective integration, HTML rendering
- Maintained elaborate system for 2-sentence release notes using separate CMS
- Fork remains open source and available for audit
- Will likely rename fork due to legal concerns
Material Icon Theme Issues
- More potentially malicious than main theme
- Contained "nasty utilities" inappropriate for icon theme
- Should be simple SVGs, not complex code with system access
- Presenter emphasizes this was the main problem, not the color theme
Creator's Behavioral Pattern
- Deleted entire source history without deleting code
- Force-pushed single commits, rewrote history 15+ times obsessively
- Attacked Zed developers on GitHub, wrote defamatory blog posts
- Made $10,000+ from Open Collective, paid himself inappropriately
- Consistently chose "worst possible action" at every decision point
- Never apologized or took ownership of harmful actions
Psychological Analysis of Online Behavior
- Humans not built for internet-scale feedback (designed for 5-10 people interactions)
- Brain overemphasizes negative feedback due to evolutionary survival traits
- Large positive attention circle creates addiction, entitlement when removed
- Creator went from small circle to millions of users, then back to negativity
- Unable to handle transition, blamed external factors instead of accepting luck
- Pattern: entitlement → harassment → malicious behavior → more negative attention
- Recommendation: go offline, return to small real-world social circles
Extension Security Recommendations
- Users should report suspicious extensions to VS Code team
- Team is responsive and takes security seriously (unlike Chrome team)
- Be careful installing extensions, audit code when possible
- Don't install extensions requesting unnecessary permissions
- VS Code team working hard to improve ecosystem safety
Resolution and Lessons
- Likely not actual malware due to creator's apparent incompetence
- Still extremely high risk profile warranting removal
- Pattern recognition important: harassment → obfuscation → malicious intent
- Community should intervene earlier when maintainers exhibit bad behavior
- Deleting project history + threatening lawsuits = major red flags
- Presenter offers redemption path if creator apologizes and takes ownership
