Update on that GitHub supply chain attack
They confirmed ~3,800 internal repos got hit via a poisoned VS Code extension on an employee's machine.
Lesson? Even big tech slips on basic extension hygiene.
My rule: Only install from verified publishers review permissions every time.
This got me thinking… How many of y’all actually review VS Code extensions before installing? But here’s the bigger issue a lot of you pointed out VS Code (and Microsoft) make it too easy to just click “Allow” once and forget. There’s no clear visibility into what an extension is actually doing in the background — especially network access, data collection, or where it’s phoning home. Microsoft has the biggest developer platform in the world. They should step up and give users real transparency tools:
• Clear breakdown of what each permission actually allows
• Easy way to see network activity per extension
• Better warnings before granting broad access Until then, we’re all just trusting checkboxes. Who else feels Microsoft needs to improve extension security visibility on their end? Drop your thoughts #CyberSecurity#VSCode#PCFix
GitHub supply chain attack got me thinking… how many of y’all actually review VS Code extensions before installing?
Quick tip: Stick to official ones check permissions. Who else is paranoid about this?
#CyberSecurity#PCFix#RigNation
GitHub supply chain attack got me thinking… how many of y’all actually review VS Code extensions before installing?
Quick tip: Stick to official ones check permissions. Who else is paranoid about this?
#CyberSecurity#PCFix#RigNation
🔥 Hidden Windows shortcut everyone should know: Win V.
It saves multiple copied items instead of just one.
Once enabled, it changes how you work on your PC.
Need remote tech help?
MicroSec® can help with slow computers, security & fixes.
#WindowsTips#PCFix