Live data from Hacker News

Microsoft's open source tools were hacked to steal passwords of AI developers

techcrunch.com

71–80 of 211 posts

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#71

And we trust these people with the root CA cert in our Secure Boot?

No one should be foolish enough to trust Microsoft with anything regarding security. They showed time and time again over the past 40 years that they don't care.

Have you bought a PC in the last 10 years? Then it came with Microsoft's secure boot keys on it. Sometimes it's not even possible to remove or disable them. Sometimes you actually need a Microsoft-signed bootloader shim to boot anything that isn't Microsoft.

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#72
post #66

Please, someone explain how it's possible to add obfuscated file to so many repositories? Do they don't have any code reviews? Also, the title is misleading, setup adds config to be auto executed by people who work on the repo. They would have to use vscode/cursor/claude/gemini. People who use codex / opencode / other harnesses are safe I guess. Details: https://www.stepsecurity.io/blog/miasma-worm-hits-microsoft-...

> Do they don't have any code reviews? I have a good friend that works for one of the giants(I can't say which one for obvious reasons but S&P 500). He's been working there for quite a while now, so far he hasn't seen what the project he works on looks like, has the repo cloned and knows what language is used but nothing beyond that. Everything is slopped together. His project is the authentication and authorization…

the reasons are not obvious. I want to avoid their products.Does anyone else *cough* who has a throwaway account know the place?

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#73
post #54

Earlier quoted context omitted.

AI;DR: Azure (49) azure-functions-agents-runtime azure-functions-connector-extension azure-functions-core-tools azure-functions-docker azure-functions-dotnet-extensions azure-functions-dotnet-worker azure-functions-durable-extension azure-functions-durable-js azure-functions-durable-powershell azure-functions-durable-python azure-functions-extension-bundles azure-functions-golang-worker azure-functions-host azure-fun…

There is such a thing as too much software.

Indeed. Every line of code is like a liability, but managers suddenly decided to stack rank developers based on number of lines of code written, again, which is like ranking aircraft designs by how heavy they are.

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#74

> steal passwords of AI developers What does this even mean? The malware specifically steals passwords from developers who use AI? From those who develop AI tool? Or it steals API tokens, which serve a similar function as passwords do for humans? Is this what journalism looks like today? Just slap the two holy letters on the title and you get views? (Yes, I read the article. No, I still don't think the title makes se…

> you can skip the slop and read the real information here: (link that is obviously written by AI)

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#75
post #66

Earlier quoted context omitted.

> Do they don't have any code reviews? I have a good friend that works for one of the giants(I can't say which one for obvious reasons but S&P 500). He's been working there for quite a while now, so far he hasn't seen what the project he works on looks like, has the repo cloned and knows what language is used but nothing beyond that. Everything is slopped together. His project is the authentication and authorization…

the reasons are not obvious. I want to avoid their products.Does anyone else *cough* who has a throwaway account know the place?

At this point, I suspect that is just about every tech company. Your best bet is to self-host everything, no agents, no cloud services, completely locked up home network and a loaded shotgun if anything starts making unexpected noises.

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#76

Earlier quoted context omitted.

Download source. Extract. Move files to correct node_modules folder. If your distribution requires more than this, then it's not really a module, or combines too many non-modular components, and should be distributed differently. The ability for npm to run scripts on any level should be removed. Then we can go back to worrying about namespacing issues.

If an attacker can infect the post-install script of an npm package, they can also infect the package source code itself. So if you ever run the project outside the sandbox, you will still get compromised. It's like saying "I don't trust a software app with an installer, I just want a .zip with the binaries from the same source that I will run myself"

> they can also infect the package source code itself

Which is where the concept of "safe levels" come in. I should be able to install this module in such a way where file operations and process operations are not available to it. That being said, presumably, this types of infiltration would seem to be _much_ easier to spot. "Why is this web framework calling 'spawn'?"

> I just want a .zip with the binaries

I want a .zip with the _code_. Just the code. None of the packaging nonsense. My distribution can handle that.

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#77
post #20

I strongly suspect this is a case of classic personal access tokens being used in an unclean way. If you are going to be handing tokens to AI agents on weird openclaw contraptions, you should try to use the fine grained variants. My GitHub account spans 3 organizations with wildly differing policies. The fact that classic tokens are even still allowed blows my mind a bit. You should be required to manually opt in eac…

I use classic tokens on low-privileged accounts for scraping public repos. I suppose organization level permissions would work fine for me.

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#78
post #32

It actually feels like nothing is safe now every day you hear about hacking is it from the ai making development weak or ai is getting strong in hacking

It was never safe to begin with, that is why the security community has been screaming for resources since the 80s.

If the security community had unlimited resources you wouldn't be able to do very much with computers. Security and usability are opposite ends of a spectrum. Either you can do a lot (usability) or you can do little (security).

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#79
post #15
post #8

guys. what the fuck. are we even doing.

getting deeper and deeper. the question is what goes one when breaches reach opensource-based stuff running nuclear reactors. i'd be concerned.

People say nuclear reactors are completely safe if properly constructed and operated and the waste danger is overblown if properly managed.

There aren't many institutions extant today that I could trust to properly construct and operate a nuclear reactor, never mind manage nuclear waste for the next 100000 years.

The Trump government just decided that there is an acceptable level to irradiate the population by the way (abandoned the linear-no-threshold model of radiation's effects on an organism)

Re: Microsoft's open source tools were hacked to steal passwords of AI developers

#80
post #23
post #16

And the best recommendation security teams can give - keep your SBOM strict, use min release age policy (sounds more like band-aid). That's a scary world to live in.

a friend of mine has a very different solution: he codes everything by hand. he says that the time you need to research to include a new package you can actually use to code the piece you need. and he for sure doesn't have the problems of transitive dependencies

That's been happening to me more often too recently. I find that, for a growing number of simple problems, reinventing the wheel is faster and more efficient than importing a mature, fully-featured dependency.
Post reply on HN