GitHub is just the latest victim of TeamPCP, a gang that has carried out a spree of software supply chain attacks.
See full article...
See full article...
What would that help? It's not Github getting compromised how these attackers do their supply-chain attacks, it's the developers' accounts and/or their CI/CD-pipelines. Banning Github would do jack shit about that.Time for people and companies to treat GitHub like Flash and ban it from their computers and development processes.
You'd have to ask them, if it actually was them. It could've been someone posing as them just as well, but...well, we don't really have any way of knowing for sure. One also has to remember that it's still a group of individuals, not a hive-mind: there could be politically motivated people there just as everywhere else and who knows? They might pull of a stunt like that without the others' permission.Anyone else find the geopolitical aside a bit strange? Why would a hacking collective that appears to be financially motivated target Iran with wipers?
It would help if they at least implemented a "cooldown", where you can set a certain amount of time that must have elapsed since the extension made a release before VSCode auto-updates the extension to that release. Alas, I cannot find any mention of any plans to implement such feature, at least not yet.Turn off auto update on your extensions if you are using VSCode or any other similar tool. It’s going to be a rough ride folks.
An excellent idea! I especially like that they request it can be managed in the enterprise. Thank you for the heads up! I’ll be upvoting as well.It would help if they at least implemented a "cooldown", where you can set a certain amount of time that must have elapsed since the extension made a release before VSCode auto-updates the extension to that release. Alas, I cannot find any mention of any plans to implement such feature, at least not yet.
EDIT: There is an open feature request for this at https://github.com/microsoft/vscode/issues/317830 if anyone's feeling like upvoting the request. I did.
It would help if they at least implemented a "cooldown", where you can set a certain amount of time that must have elapsed since the extension made a release before VSCode auto-updates the extension to that release. Alas, I cannot find any mention of any plans to implement such feature, at least not yet.
EDIT: There is an open feature request for this at https://github.com/microsoft/vscode/issues/317830 if anyone's feeling like upvoting the request. I did.
It's starting to feel like: if you have a machine that's been stable and nothing on it updated for a while, do NOT accept or download any new apps or updates, other than vetted OS security updates. At least until this gets sorted somehow. And maybe Firefox updates, since they seem to be keyed in on fixing security holes at the moment and presumably would vet their own Fox food before sending it out into the world.Literally EVERYTHING that was promising about the Internet Information Superhighway is being compromised or destroyed. It lasted a good 25 years, but now we're entering the true end stage.
Maybe dev shops should now explicitly state on every product page, "only download direct from our site or the app's direct update mechanism (which goes to our site), as only those can be verified as having been scanned and vetted before release."
Good thing all the major OSes are based in a country whose government obeys the rule of law...That's why code signing exists and is integrated into modern OS
I can't wait for you to explain how, exactly, that would help with any of this.Perhaps this type of crime should be a capital offense?
Tempting and appealing on a certain level, but no. Capitol punishment doesn’t work because those doing this sort of thing are arrogant enough to believe they won’t ever be caught, and most aren’t.Perhaps this type of crime should be a capital offense?
On Tuesday night, open source code platform GitHub announced that it had been breached by hackers in one such software supply chain attack: A GitHub developer had installed a “poisoned” extension for VSCode, a plug-in for a commonly used code editor that, like GitHub itself, is owned by Microsoft.
You do understand that Microsoft has contracts with the Israeli government.Anyone else find the geopolitical aside a bit strange? Why would a hacking collective that appears to be financially motivated target Iran with wipers?
Accuse me of tinfoiled fashion accessories if you like, but I'm willing to wager that TeamPCP is bankrolled by Mossad.
Why would the Russian government outlaw one of their most important sources of revenue?Perhaps this type of crime should be a capital offense?
A bit before my time, but I miss the era of hitting up niche forums and blogs for third party software. Felt like the wild west, compared to today, but I trusted those forums more than I did limewire.Who remembers when a developer had updates and you sent in for them on floppies via snailmail?
No hacker trying to intercept your postal mail to infect that floppy... when RAM was in K and Megabytes not Gigs...
Speed and convenience over security.What would that help? It's not Github getting compromised how these attackers do their supply-chain attacks, it's the developers' accounts and/or their CI/CD-pipelines. Banning Github would do jack shit about that.
Just as an example, many of these attacks have happened because some projects like to run a CI/CD-pipeline on any new pull-requests to check for compilation errors or other issues, but they've given the pipeline access to tokens they shouldn't have and/or wider permissions to the project's repos than intended, so a malicious pull-request could abuse this and cause the pipeline to write to the repos and/or leak the tokens. That's not Github's fault, that's the developers' own mistake.
PCP did so because an Iranian in a specific Telegram chat was posting annoying content, and this was simply to get a lol and assert his hacking skills for accolades in the group chat.Anyone else find the geopolitical aside a bit strange? Why would a hacking collective that appears to be financially motivated target Iran with wipers?
Accuse me of tinfoiled fashion accessories if you like, but I'm willing to wager that TeamPCP is bankrolled by Mossad.
The headquarters of Canonical (the company behind Ubuntu) are in London, England.Good thing all the major OSes are based in a country whose government obeys the rule of law...
I must be far too old school: was amazed to realize that people just blindly auto update their dependencies.It would help if they at least implemented a "cooldown", where you can set a certain amount of time that must have elapsed since the extension made a release before VSCode auto-updates the extension to that release. Alas, I cannot find any mention of any plans to implement such feature, at least not yet.
EDIT: There is an open feature request for this at https://github.com/microsoft/vscode/issues/317830 if anyone's feeling like upvoting the request. I did.
Don't vibe code - it's a bloody stupid idea anyway. Understand what you're writing, understand what your LLM is writing!If I'm a home vibe coding user what's the best way to protect myself from these sorts of things?
The discussion is about IDE extensions, not code dependencies.I must be far too old school: was amazed to realize that people just blindly auto update their dependencies.
I must be far too old school: was amazed to realize that people just blindly auto update their dependencies.
If I'm a home vibe coding user what's the best way to protect myself from these sorts of things?
Vibe code! Have fun. Let the AI do the boring thing you are not interested in. We all know its limitations by now.Don't vibe code - it's a bloody stupid idea anyway. Understand what you're writing, understand what your LLM is writing!