Top stories

Live mirror
30 storiesupdated 0s agoView source snapshot
  1. Introducing System One Models and Jev(typesafe.ai ↗)
    177comments
  2. Show HN: An e-ink frame that hears birds and draws them as 1800s illustrations(github.com/arnegiacomo ↗)
    158comments
  3. German Rheinmetall open-sources its Battlesuite connected weapon system protcol(rheinmetall.github.io ↗)
    12comments
  4. An Update on Wayback Machine Access(blog.archive.org ↗)
    160comments
  5. Jean-Pierre Serre is 100 years old today(st-andrews.ac.uk ↗)
    9comments
  6. Gemini 3.8 Live and 3.8 Live Extended Thinking(blog.google ↗)
    152comments
  7. We got admin access to Baseten's production GitHub in 25 minutes(strix.ai ↗)
    86comments
  8. Building a Linux GPU Driver for the M4 Mac Mini in One Month(codyho.dev ↗)
    30comments
  9. Chopping up books when they're physically too big(mattkirkland.com ↗)
    79comments
  10. WangNet – 1.8 MB, zero-dependency Numberwang adjudication in 11 languages(github.com/graafhenk ↗)
    29comments
  11. I can't stop thinking about Papua New Guinea(notnottalmud.substack.com ↗)
    405comments
  12. Show HN: Capsule – Single-file web apps that save their data into SQLite(withcapsule.app ↗)
    112comments
  13. Data races and the limits of ThreadSanitizer in C and Go(theconsensus.dev ↗)
    1comments
  14. GEFS on OpenBSD: A Early Preview(marc.info ↗)
    49comments
  15. Vibe Coding is the new Internet Dating?(joecmarshall.com ↗)
    29comments
  16. Learning to solve hard problems in RL for LLMs by never giving up(mnoukhov.github.io ↗)
    discuss
  17. Jiga (YC W21) Is Hiring Product Engineer (Remote/US)(jiga.io ↗)
    discuss
  18. Let's make quality the norm again(forbrukerradet.no ↗)
    277comments
  19. The CSS Zen Garden dream, finally shipped(josprague.com ↗)
    53comments
  20. Suspected sabotage causes major Netherlands rail disruption(bbc.com ↗)
    376comments
  21. Show HN: Pizza Bot – An inbox for AI agents that work in the background(github.com/pizza-bot-app ↗)
    2comments
  22. Cartesian – AI 3D Modeling for Design(formas.ai ↗)
    66comments
  23. Why I'm still bearish on LLMs after Navier-Stokes(dank.systems ↗)
    1comments
  24. Show HN: Hacking a $20 4G wireless hotspot into a texting device(bkovac.github.io ↗)
    30comments
  25. A single firm is behind OpenAI, Anthropic, and Meta hacking scandals(effort.news ↗)
    132comments
  26. The Inference Hardware Revolution of 2026(ieee.org ↗)
    9comments
  27. Most people prefer traditional architecture(worksinprogress.news ↗)
    181comments
  28. US confirms for first time it has deployed space weapons(bbc.com ↗)
    287comments
  29. Giving up on smart rings(notesbylex.com ↗)
    129comments
  30. 25 years of mass surveillance is enough(schneier.com ↗)
    267comments

We got admin access to Baseten's production GitHub in 25 minutes

167 pointsby 4h agostrix.ai
85 comments
4h agoHN ↗

We were (and still are) considering them as an inference provider and did a quick check first... but kudos to their team for the fast patch

4h agoHN ↗

We really are entering the AI economy.

Now if only we knew if the stonks would go up or down (due to global turmoil) before I throw my savings at the SPY

4h agoHN ↗

Right now Trump is the wild card you have to take in account. He’s influencing the SPY way more than the AI trade

4h agoHN ↗

Baseten handled this well. The timeline was:

July 13, 11:10 PM: I reported the live basetenbot token, the public Harbor project, and the repository permissions.

July 14, morning: Baseten made the Harbor project private. I flagged that the token itself still worked.

July 14, 4:34 PM: Anton from Baseten Security confirmed the issue as critical and said they had made the Harbor project private and rotated the token. He also asked us to securely delete the images we'd pulled.

July 14, 5:05 PM: We confirmed deletion and sent over two lower-severity findings from the same scan.

July 17: Baseten closed out the remaining findings.

September: We let Baseten know we planned to disclose the finding publicly and sent them a draft of this post.

They also sent us some T-shirts and sweatshirts as a thank-you for finding this critical bug.

well done all around. i think my only open question is what default security boundaries should all vibecoded internal agents follow as a learning we can take from this

3h agoHN ↗

Good in terms of prompt communication and fix. Absurdly bad in terms of reward.

Earlier in the article, it mentions that Baseten is valued at $13B. They can't dig into their couch cushions to give a few thousand dollars to the researcher privately disclosing a bug that let an attacker escalate to admin in their GitHub org?

This sends the message that honest researchers should not waste their time looking for vulnerabilities in Baseten, but it's a good target for criminals who want to monetize these vulnerabilities.

3h agoHN ↗

Yeah companies need to quickly understand that having good actors try and hack you is a good thing - those hacks get reported and another door gets sealed shut for bad actors.

This is more true today than ever before as the bar for a successful attack has never been lower. We’ll see a resurgence of the script-kiddie, or shall I say, vibe-kiddie :-/

3h agoHN ↗

Swag packages like these are a token of appreciation not a reward.

The front page post in HN here is worth far more than few thousand dollars , don’t think either organization is operating under purely financial transactional nature .

Most people who find a dropped wallet will return it without evaluating the market value of your compromised identity or the contents of the wallet .

Grateful owners may buy you a beer that doesn’t make them cheap , not everything is evaluated in purely money terms, and that is a good thing ?

2h agoHN ↗

Thank you for pushing back on one of the top disruptive bad-faith comments we see on HN.

The follow up arguments will be that since billion dollar companies ultimately only care about their bottom line, so should we.

I'm certain most of these comments mean well (to "open eyes" or whatever), but some of them really are on principle and blatant astroturfing.

2h agoHN ↗

It's nice to wax poetic, but they should absolutely pay the researchers here.

2h agoHN ↗

The follow up arguments will be that since billion dollar companies ultimately only care about their bottom line, so should we.

so it should be fought by giving them free work in the hopes that they'll finally feel guilty and then start paying proper bounties?

like to me that just seems funny, as if they'd change anything if we'd keep rewarding them for not doing the right thing

like, there's a reason regulation exists for all kinds of shit because otherwise companies would do all kinds of atrocities in hopes of cutting costs

36m agoHN ↗

At some point, you will realize two things.

First, you're being petty and just fighting fire with fire. Second, most of this research is fairly trivial.

What you're instead encouraging is a race to the bottom. You're not going to kill off the companies you hate by withholding information. You don't even have that power anyway because by its very nature, security research is not secret. You're really just encouraging pessimistic groupthink and bad faith. This is why businesses can't be more open about their flaws. It's not that they're stupid and incompetent, but that the pitchforks come out. These are the seeds of dystopia.

They would have eventually figured it out, but as an unfortunate incident with an outsized effect. As much as you wish it to be true, even the worst of these incidents will not kill their business. As much as you hate these businesses, their financial momentum will eventually cause the public to depend on them more. There's more at stake here than anyone's personal gain. It's naive to think otherwise.

You're just manifesting broken windows and ignoring litter thinking you're fighting the man. This is straight up ghetto punk ass behavior wearing a white collar.

2h agoHN ↗

Wallets usually belong to real people with lives. We can empathize with them. Companies are not people. And they also don't and can't empathize with you.

1h agoHN ↗

"and can't empathize with you" - I don't really understand why such a perception of companies has been regurgitated and reinforced so much in US public, to the point where it's a blank excuse from ever expecting such a thing from a company. It's not true that it can't. The only reason to keep repeating that kind of worldview is to absolve companies behaving in shitty, toxic or downright evil ways.

The law doesn't say companies MUST choose the most profitable choice at every turn, and even explicitly allows for good treatment of customers, community, employees etc as a viable business strategy (even if it's sad that it must be justified in that way).

1h agoHN ↗

I think the point is that companies are purely legal entities, and as such, cannot feel, much less empathize, simply by virtue of them not being living things

6m agoHN ↗

That's nonsense. "Companies" are not something non-human, they are run by humans, who do feel, empathize, and are living beings. Without these living-being humans, there would simply be no "company".

Now how those humans that run the company behave is another thing - they are free to be greedy assholes, and a lot of them are, and some of them aren't - but that's still a human thing.

20m agoHN ↗

I agree that this notion that companies make these decisions is bad, bad on the grounds that it's people working for those companies that make the decisions, they hide themselves away, but the company itself isn't doing anything - is always a human making the decision

2h agoHN ↗

The front page post in HN here is worth far more than few thousand dollars , don’t think either organization is operating under purely financial transactional nature .

not always, especially if its just someone independent. iirc there was a guy here not too long ago who started dropping Windows 0days because Microsoft couldn't be assed to process his bug reports

53m agoHN ↗

That actually supports the point that people aren't acting under purely financial motivations. If the guy was purely following financial motivations, surely he would have chosen to sell the vulnerabilities to the shadier side of things. Instead, he dumped them publicly, burning their value while amplifying the "fuck you" factor to Microsoft.

Ignoring reports, or just fixing the vulnerability without acknowledging the work put in by a researcher, is rude and invites rudeness in return.

31m agoHN ↗

Microsoft runs a bug bounty program. NightmareEclipse (that’s the researcher’s handle) allegedly participated and Microsoft did not honor their part of the bug bounty program terms.

This is a completely different situation - a company evaluates the security of a prospective vendor prior to entering a business agreement.

2h agoHN ↗

of course not, all they can do is a lil "thx"

This sends the message that honest researchers should not waste their time looking for vulnerabilities in Baseten, but it's a good target for criminals who want to monetize these vulnerabilities.

of course, these companies want you to sell vulns to brokers and other orgs. they don't care about bug reports.

otherwise they'd pay as much or even more, right?

40m agoHN ↗

The researcher in this case was doing a security review for their company who was a potential customer. Sending potential customers more than a token amount of cash is usually prohibited by corporate ethics rules for obvious reasons.

3h agoHN ↗

They also sent us some T-shirts and sweatshirts as a thank-you for finding this critical bug.

Honestly I would have held out for a (hard to get) hardcover copy of Inference Engineering.

2h agoHN ↗

I’d treat a vibecoded agent like an untrusted CI job, not like a junior employee: repo-scoped identity, read-only by default, no inherited Actions token or production secrets. Any operation that turns a read into a write should require approval outside the agent’s control and produce an auditable diff. Network egress belongs in the boundary too. Read-only access is not much protection if the agent can send everything it reads to an arbitrary endpoint.

1h agoHN ↗

This is probably still considered standard response timeline, not a rapid one.

The time window allowing for CVEs + Vulnerabilities remediation has been collapsing to days and hours perhaps even minutes[1]. Anyone who has an OpenRouter account can start using Strix + GLM 5.3 Flash to do damages at frontier Mytho 5 level cyber capabilities. [2]

This cyber patching race is on, won't stop until all the software created for the past 70 years still in active use needs to be patched up. This is happening at EVERY SINGLE software company.

The cost of not doing it? Game over.

[1]: https://news.ycombinator.com/item?id=49699402

[2]: https://news.ycombinator.com/item?id=49705036

1h agoHN ↗

Meanwhile I have customers running legacy web apps last compiled over five years ago on end-of-life operating systems… and it’s crickets chirping. Dead quiet, not even a hint of an attack, let alone a breach.

I expected them to have been hacked to pieces by now, but even “maximally vulnerable” internet-facing apps seem to be relatively unmolested so far.

Maybe it’s still too expensive to go after “boring” enterprise targets? Maybe the bad actors targeted crypto systems first for the immense payoffs, if successful?

4h agoHN ↗

i quite liked using strix. last time i tried it, deepseek was a mess and bloated the context with nonsense. that was ~5 months ago, i wonder how it performs now

3h agoHN ↗

We've made a lot of awesome changes recently, would love any feedback on the latest version :)

4h agoHN ↗

This sounds interesting and twisted in some sense

1. A start up is validating a service provider to ensure that they are secure enough so that they can trust them before signing up for their service

2. The service provider is already trusted by so many big name companies who handed over their data, the customers data to them

Should it not be other way around?

On a different note, the finding is not just one off absolute, rather its a symptom which points to certain experience and expertise level for security practices. To be fair its hard to blame the start up folks, they are running against time and cutting corners is somewhat critical for survival for their business

4h agoHN ↗

That is great marketing for strix, pretty bad for baseten. I don't think someone can have a better story to advertise their own security product. Did not know about strix but I am going to look it up now. Might add it to my stack.

3h agoHN ↗

Let us know if you have any feedback!

3h agoHN ↗

If I enter an address to "Start testing", I expect at least a preview of the report rather than being dumped on the signup page.

3h agoHN ↗

Yeah understood — we need to make sure you own the domain first though

51m agoHN ↗

Is there a sample report somewhere to get a feel for the output?

3h agoHN ↗

Yeah I have seen this issue a few times. If you use Docker build arguments that way add `--provenance=false` to get rid of all that build metadata. Build secrets are still better since they allow you to scope the secret inside of the Dockerfile. Also, the metadata can be useful to inspect images.

3h agoHN ↗

Yeah honestly I wasn't too familiar with this beforehand but now have a sense of the best practices going forward

3h agoHN ↗

Baseten carries the Soc 2 Type II and HIPAA Compliant logos on its front page. They also have logos for customers including: OpenEvidence (medical related, used by almost 2/3 of physicians in the US, claim HIPAA compliance), Harvey (legal related, claim "binding terms on data protection, data access, incident response SLAs, and other controls aligned with SOC2, ISO, GDPR and other standards.")

From TFA:

That token had admin and push access to Baseten's main product repo, the GitOps repo that drives their clusters, and their Homebrew tap, plus read/write access to other private repositories including specific repos per customers.

The image build dated to March 2023, and the token still worked when we found it in July 2026.

What are the legal implications here?

3h agoHN ↗

Unless github had regulated data, unlikely, the legal implications are few. Document the issue, remediate and no findings on the next audit. Done.

3h agoHN ↗

Given the build is from 2023 one would expect that at least the token would have been rotated, and I suspect some of these compliance checks do require rotation of tokens/passwords.

That said, the whole compliance industry is a joke.

3h agoHN ↗

A Markdown-as-a-Service where the interface is a Docker container.

I get how these choices might be the local optimum for a desired UX, but damn is it depressing to extrapolate where software as a whole is going.

3h agoHN ↗

I wonder what model was used for this. Also as far as I know Baseten does not have any abliterated models in their repertoire.

3h agoHN ↗

Either Mythos 5.1 or GPT 5.6 Cyber (aka. GPT Daybreak Red)

2h agoHN ↗

Chinese? I can not imagine how a western state of the art model would follow through with such a task and not require some major trickery.

3h agoHN ↗

The bot snippets talk claudish. I'd say Opus 5. But they must be Cyber Verification Program approved by Anthropic I suppose for the LLM not to block them.

2h agoHN ↗

Hate to burst your bubble but wasn't Claude......

3h agoHN ↗

An easily preventable issue with proper engineering culture around defense in depth and principle of least privilege, awful look on Baseten here.

Kudos for Strix to find it, and especially with how it chose to disclose and report it.

3h agoHN ↗

[pen-testing agent] came back with an active GitHub personal access token for basetenbot. That token had admin and push access to Baseten's main product repo, the GitOps repo that drives their clusters, and their Homebrew tap, plus read/write access to other private repositories including specific repos per customers.

And the agent found the token in Docker build history after finding a Baseten image repository.

I wonder how many of these kinds of agent-driven security exploits we're not hearing about these days (i.e. driven by bad actors), worrying.

3h agoHN ↗

Is this legal? I know I can’t try and break into my neighbors house even if I have no intent of going inside and stealing once I break the lock.

2h agoHN ↗

I know I can’t try and break into my neighbors house even if I have no intent of going inside and stealing once I break the lock.

They didn't break in. They found a key that their neighbor dropped and returned it.

Is this legal?

Generally, yes (though ask a lawyer if you're going to do security work). Security researchers do occasionally get legal flak though, depending on which idiot they annoy by pointing out issues.

1h agoHN ↗

IAAL (not legal advice, consult a lawyer in your jurisdiction). You really do not want to pen-test a target without their permission. If you're identified as a culprit, the Feds will shove the CFAA so far up your ass you'll need a proctologist.

27m agoHN ↗

as a lawyer, can you speculate as to why anthropic/openai aren't facing many or any consequences for their agents? I'm not asking in a "grab the pitchforks" way. more out of genuine curiosity as my uninformed recollection of the CFAA is as you describe it.

2h agoHN ↗

It's not, in most juridictions at least, but it would be insanely stupid for baseten to sue (and the hacker would probably not get much more than a slap on the wrist given that they weren't malicious).

2h agoHN ↗

It's not, in most juridictions at least

What did I miss they did that's illegal? It looked like it downloaded a public docker image, searched around inside, and verified that the key it found was still valid (without making any changes), and then immediately notified them about the issue.

2h agoHN ↗

If there is anything that was a crime (and it totally depends on jurisdiction), it was verifying the key. They used it to see what it could access, and by using it they had unauthorised access to a system

51m agoHN ↗

The CFAA is broad enough to make that a crime.

1h agoHN ↗

People have been arrested for far less. I dunno what the least offensive conviction has been though tbf. Anyone know?

18m agoHN ↗

Suing is not what you do when someone commits a crime against you. You're confusing civil law and criminal law.

2h agoHN ↗

It's implied (but sadly not stated) in the post that they asked for baseten's permission before conducting this research.

What's interesting to me as someone who has sold a lot of software to a lot of software companies is that many enterprise vendor agreements explicitly allow companies to pentest their vendors with advance notice and coordination. I don't think any of our clients ever exercised that clause; I expect it's going to be exercised a lot more going forward because it's so easy to do now.

1h agoHN ↗

They probably negotiated a "permission to attack" before letting Strix off the leash, as pentesters usually do.

34m agoHN ↗

when t̶h̶e̶ ̶P̶r̶e̶s̶i̶d̶e̶n̶t̶ an AI company does it, that means that it is not illegal.

- AI Richard Nixon

3h agoHN ↗

We build Strix, an autonomous hacking again.

But... we're a security company.

So... we pointed Strix at *.baseten.co and let it run without credentials or source code.

lawyers wet dream. and a perfect case. A security company who KNOWS the law unleashed an AI agent to violate the laws

2h agoHN ↗

A lawyers wet dream is when a security company.... Finds an issue, does not abuse it, and reports it to the affected party for it to be patched?

I feel like people like you are more of a lawyers wet dream, in that they'll happily litigate a frivolous case for you while billing you hourly.

2h agoHN ↗

Feelings don't really matter in the legal world. Statements and actions do.

2h agoHN ↗

if i find someones key on the ground and take the key and walk into their house and poke around, and make sure to leave a letter, this is a good thing?

2h agoHN ↗

Agreed. Pretty sure you are supposed to ask for permission before pentesting someone. Hopefully they, being a security company, know that.

3h agoHN ↗

Just signed up for strix, is it common for these type of products to want access to my Github repo's? Shouldn't the attack surface be outside them?

3h agoHN ↗

You can also just do an external pentest -- Github is for continuous CI/CD coverage

2h agoHN ↗

So Strix enumerated hosts, looked through certificate logs, mapped the full surface.

If there is anything that you should do while setting up infrastructure... it is getting rid of single-host SSL certificates. If you're on Amazon... just let it issue wildcard certificates and place an ALB in front of hosts that terminates the SSL connection. The very second a subdomain appears in any of the CT logs directly, you've lost, it will get hammered.

And keep your public and private Git, Docker, npm and whatnot registries separate infrastructure, with the private stuff only reachable from within the corporate network, preferably just servers. Too many a company got hacked and lost significant data because of someone exploiting a GitLab RCE on an instance that hosted both private and intentionally-public repositories. (Yes, I have been there.)

It is their GitOps: the repository contains the desired state of the clusters, and it applies that state to the infrastructure.

That's another thing I frankly do not get why people are still doing it.

It's fine to have a Git pipeline do a lint, even a terraform plan using a read-only token (although that token needs access to the statefile aka s3 bucket... and there will be relevant secrets there). But, IMHO, a terraform apply should always, always be run on a machine of a sysadmin manually doing the apply. A human, you can hold accountable, and you can keep them at a good security posture with short-lived session tokens. But a Git pipeline where there is a cloud provider token with full admin permissions? That is one Gitlab RCE patch or Github issue away from being compromised.

Besides, one repository holding all the IaC stuff? That just sounds like hour long `terraform refresh` sessions.

2h agoHN ↗

So often recent breaches involve Github in one way or another. How is it still considered a sane choice to host anything proprietary there? If your business is built around open source, ok, put a mirror on Github. But CI/CD, gitops, FDEs' stuff have no place on a public cloud. C-level execs may not know bits from bytes, but by now they should've understood that this is akin to storing ammonium nitrate in the open air.

2h agoHN ↗

This wasn't GitHub's fault in any way.

16m agoHN ↗

So many security breaches involve Linux in one way or another. Your argument doesn't really work.

2h agoHN ↗

It may make sense to change security practices so nothing has long term access. Everything should be rotated monthly, and maybe within a few years, hourly.

1h agoHN ↗

…by finding an admin token in logs.

59m agoHN ↗

cannot delete the card from billing.

55m agoHN ↗

Always check. I used a disk wiper , I checked the disk sectors, bang files under 1kb not really wiped...my "secrets" case..

37m agoHN ↗

Whether it's valid or not, there is something that rubs me the wrong way about a security tools company using a real customer/vendor as a marketing campaign. This "story" could have been told without naming, bluntly, their "victim".

It would be different if it was some complex, multi-step exploit, but the tone is closer to "look how much Baseten fucked up!".

Strix also crossed the line at this point:

Strix decided to pull an image and see what was inside.

You're going past the white-hat point here when you start active exfiltrating data and looking at it. Once you start using credentials from the exfiltrated data and start listing and poking around internal systems, you are way past it.

Listen, I get it, their product is "meant for" self-testing, so it assumes it's safe to go digging. After all, it's a self check. That is exactly why it's irresponsible, and borderline illegal, for them to point it at a third party. Even if they had "permission", I dobut that permission extended to "and also search and/or download our repos if you can".

The overall tone is less than professional. Statements like (in bold) "This is an insane amount of access to leave in a publicly downloadable image." Everyone is aware of this, and it's phrase like it was a purposeful decision.

Security tools from teams that actively shit on the people they're designed to "help" feels wrong.

Edit: For clarity on my point about "pulling repos", this post includes descriptions of the purpose and functionality of multiple repos (which is past what a name gives them), and they explicitly state: "A listing of that private repo showed a top-level customers/ directory, with subdirectory after subdirectory named after Baseten customers". Strix explicitly took action that they knew they were not permitted, and extracted confidential customer information. Claiming "We didn't clone the customer repo" when you, instead, just listed the contents of the repo, is not a valid defense.

18m agoHN ↗

Agreed. I suppose they'd have slightly less credibility by saying "we hacked <unnamed company>" but it strikes me as far classier than naming & shaming.

22m agoHN ↗

It should be illegal to produce software products that people will depend on and are this blatantly insecure