151–160 of 424 posts
Looks like he's responded to it here. Delusional maniac? (Also, don't download and install that file he links) https://github.com/material-theme/vsc-material-theme/discuss...
Is the original source code still uploaded somewhere?
Hey y'all, I made the most prominent fork of this extension "Material Theme (But I Won't Sue You)" The maintainer went off the deep end last year. He pulled the (originally apache 2) source offline, then started threatening to sue people for hosting alternative versions, including them in other IDEs, etc. Genuine lunatic. Out of an abundance of precaution, I've taken the following action on my fork: 1. I have the VS…
To me it seems ridiculous, that a theme could even accumulate such things as analytics and even lots of dependencies. A theme is usually something self-contained. And even more ridiculous, that anyone can, as you write, "force uninstall" anything from my machine. So glad I am not a VS Code user. It seems all the typical corporate BS is happening with its marketplace and plugins.
Earlier quoted context omitted.
This is tracked in this feature request https://github.com/microsoft/vscode/issues/52116 We do not plan to add a permission model in the next 6 months.
> We do not plan to add a permission model in the next 6 months. I guess Copilot functionality trumps "Security above all else" now. https://blogs.microsoft.com/blog/2024/05/03/prioritizing-sec...
Now they are all “copilot” “features”.
Someone uploaded a replacement, Material Theme (But I Won't Sue You) https://marketplace.visualstudio.com/items?itemName=t3dotgg....
Looks like the creator of the replacement is the tech YouTuber theo ( https://m.youtube.com/@t3dotgg )
What is it about material themes that does this to people? The same kind of thing happened to the IntelliJ one half a decade back. At least that one wasn't literally just colours.
Hi - Isidor here from the VS Code team. A member of the community did a deep security analysis of the extension and found multiple red flags that indicate malicious intent and reported this to us. Our security researchers at Microsoft confirmed this claims and found additional suspicious code. We banned the publisher from the VS Marketplace and removed all of their extensions and uninstalled from all VS Code instance…
Letting you know that VSCode is unable to uninstall the extension. It prompts me to uninstall, but when I confirm the window refreshes and the extension is still there, triggering the same "is problematic" prompt. This is an infinite loop. Same behavior when trying to uninstall the usual way from the extensions panel. I had to manually delete the extension's folder in %USERPROFILE%\.vscode\extensions and delete the e…
This HN submission now links to a 404 on github. Is the original source code still uploaded somewhere?
Hi - Isidor here from the VS Code team. A member of the community did a deep security analysis of the extension and found multiple red flags that indicate malicious intent and reported this to us. Our security researchers at Microsoft confirmed this claims and found additional suspicious code. We banned the publisher from the VS Marketplace and removed all of their extensions and uninstalled from all VS Code instance…
Hi Isidor, excited for this! At Open VSX, we'd love to take a look and potentially flag the extension as malicious on our side as well. Are you aware of the version range that the malicious code was included in? I'm asking because https://open-vsx.org does not have any version published since the extension went closed-source.