Anthropic Unveils ‘Claude Mythos’ – A Cybersecurity Breakthrough That Could Also Supercharge Attacks : cybersecurity@sh.itjust.works

There may have been a time where advertising was honest but nowadays, the Help Desk rule applies "never believe a customer unless they are confessing".

If a company is making a claim that benefits them, you cannot believe it without independent, third party corroboration. If they are confessing to wrong doing, you should assume it's 10x worse than what they are stating.

permalink

fedilink

source

parent

[–] GamingChairModel@lemmy.world 4 points 7 months ago (8 children)

The security blog writeup is here:

https://red.anthropic.com/2026/mythos-preview/

They've described several patched CVEs and disclosed the hashes of writeups that are currently undergoing the responsible disclosure process.

It lists quite a few, so I'll be checking back when the vulnerabilities/exploits are patched and disclosed.

permalink

fedilink

source

parent

hideshow 8 child comments

[–] Jhex@lemmy.world 2 points 7 months ago* (6 children)

From the blog's site:

About the blog

Welcome to red.anthropic.com, the home for research from Anthropic’s Frontier Red Team (and occasionally other teams at Anthropic) on what frontier AI models mean for national security. We provide evidence-based analysis about AI’s implications for cybersecurity, biosecurity, and autonomous systems.

This is Anthropic paid people, peddling Anthropic successes...

permalink

fedilink

source

parent

hideshow 6 child comments

[–] GamingChairModel@lemmy.world 7 points 7 months ago (5 children)

Yes I understand, but I'm also putting the direct claims right there, not filtered through Anthropic's PR or an article from the IT industry press interpreting those PR statements.

These are real CVEs that have actually been submitted to the code maintainers for both FOSS and closed source software that is foundational to the computing world. Some of them are published in this post. And many more are simply described with a hash of the full writeup indicating that they have it written out and are waiting for the patches to be applied. I'm especially interested in the Virtual Machine Monitor and the exploits for jumping out of browser sandboxes for "all major browsers."

Some of the published CVEs in the blog post seem pretty serious, especially the FreeBSD remote root access for devices running NFS. The OpenBSD one is a critical DOS vector, and the FFMPEG one is just a bug that doesn't seem to actually expose the software to any practical exploits but should still be patched.

But they've staked it out with their public disclosure of the hashes and a description of a few of the problems. These are big bold claims that are provided in a format that will be easily falsifiable in due time. And treating it as just marketing fluff ignores the shades of gray that actually apply to corporate claims.

permalink

fedilink

source

parent

hideshow 5 child comments

[–] Jhex@lemmy.world 0 points 7 months ago (4 children)

Yes I understand, but I’m also putting the direct claims right there, not filtered through Anthropic’s PR or an article from the IT industry press interpreting those PR statements.

How do you know Antropic's PR is not in this? certainly all these employees have signed NDAs about inner workings of the company they work for. Do you really think any of them would post something like "yeah, we found a vulnerability but it's basically a typo that could not be seriously exploited"?

These are real CVEs...

Regarding this... I just saw another post where people were challenging ffmpeg about accepting PRs from Anthropic and their answer was that the PR were written by humans, not any of the Anthropic Ai, so even if the whole scenario is real, it may not have the intervention of Ai they are claiming

... And treating it as just marketing fluff ignores the shades of gray that actually apply to corporate claims.

This is really a corporate problem of their own making and their responsibility to fix. They have lied so much, I do not owe then a single iota of trust.

If they want to be trusted, they should be truthful. It's really that simple

permalink

fedilink

source

parent

hideshow 4 child comments

[–] GamingChairModel@lemmy.world 2 points 7 months ago (3 children)

This is really a corporate problem of their own making and their responsibility to fix. They have lied so much, I do not owe then a single iota of trust.

The statements can stand for themselves, evaluated on the merits of the claims, regardless of authorship. That's how these things should work. Someone who has a great history of finding vulnerabilities still has to stand by each exploit/proof of concept they write, on its own merits. On the flip side, the corollary to the adage that a broken clock is still right twice a day is that you can't just say "oh the broken clock said this so I can ignore it."

Do you really think any of them would post something like "yeah, we found a vulnerability but it's basically a typo that could not be seriously exploited"?

The blog post literally describes exactly that, for ffmpeg. And several of the other described vulnerabilities sound like they're in that category of "here's a bug but we didn't find an exploit."

Simply refusing to engage with these big claims just because of the source is an irresponsible way to approach cybersecurity.

even if the whole scenario is real, it may not have the intervention of Ai they are claiming

...who cares? If it's a real bug and a real PR addressing the bug, why does authorship or methodology matter?

It's just the ad hominem fallacy (or the close relative, appeal to authority). Let the actual substance stand and fall on its merits. Read the described vulnerabilities and exploits and decide whether you think those need to be patched and how critical/severe the bugs/vulnerabilities are.

And maybe your priorities are different from mine, but the core of the claim (we found some vulnerabilities) trigger a responsibility to address them (confirm and patch). I don't care about marketing or corporate interests or whatever in those circumstances, I'm just focused on fixing problems that have been found.

permalink

fedilink

source

parent

hideshow 3 child comments

[–] Jhex@lemmy.world 0 points 7 months ago (2 children)

The statements can stand for themselves, evaluated on the merits of the claims, regardless of authorship.

Sure but where is the practicality of that? According to your POV here, companies can claim whatever and it's my job now to figure out if they are lying or to what extent. I have already lived through that and decided their output is completely untrustworthy so I rather wait for a trustworthy source before giving them any credit. I am not claiming 100% of what Anthropic says is a complete lie, I am saying I cannot trust it at face value.

On the flip side, the corollary to the adage that a broken clock is still right twice a day is that you can’t just say “oh the broken clock said this so I can ignore it.”

Funny you use this saying because a broken clock is never right, reality momentarily aligns with it, which is a completely different thing... and even then, for every minute of the day, a clock is still wrong 1438 times a day... I would rather not use suck broken clock as a reference AT ALL

The blog post literally describes exactly that, for ffmpeg. And several of the other described vulnerabilities sound like they’re in that category of “here’s a bug but we didn’t find an exploit.”

Case in point, they do not claim that in the title or intro. Their entire intro (in the blog you posted) is all about how amazing Mythos is

…who cares?

People like me who rather not keep feeding the Ai hype. Assuming these vulnerabilities are real and could have been exploited, yes I am happy they get fixed. But I am never giving credit to "Ai" unless it is an absolute certainty Ai did it and did it better than humans would

permalink

fedilink

source

parent

hideshow 2 child comments

[–] GamingChairModel@lemmy.world 1 point 7 months ago (1 child)

According to your POV here, companies can claim whatever and it's my job now to figure out if they are lying or to what extent.

No, the actual claims here, that describe specific bugs in specific software, can be evaluated. Even without whipping out a test environment to try to reproduce the results with your own proof of concept, you can read the text and evaluate whether the claims make sense on their face.

a broken clock is never right, reality momentarily aligns with it, which is a completely different thing

And that's why the substance of a statement matters. I don't believe in the supernatural, so if someone says "I'm a psychic and the missing girl on the news is in a shed near the water," that doesn't register with me at all. But if that person says "I'm a psychic and the missing girl is in a shed at 1234 Main Street" that raises eyebrows because it is easily falsifiable. And if the person says "I'm a psychic and the missing girl is in a shed, so I looked and found her and reported it to the cops, and here's a cryptographic hash of my description of how I found her, which I'll publish once the cops confirm she's safe" that's gonna be a much more serious statement. Even if I don't believe that the person actually is a psychic, I can pay attention to how the whole thing played out because the person claims serious non-psychic validation of the results, and the results themselves are important entirely externally from the claim of whether psychics have powers.

This is a story about several cybersecurity vulnerabilities, some of which sound medium or high severity in very commonly used software. That's important in itself, outside of AI mattering at all. And if they claim to have the receipts in a falsifiable way, that's the kind of thing that shows a high degree of confidence in the genuineness of what was found.

I don't give a shit about AI and I'm generally a skeptic of the future of any of these AI companies. But if someone uses AI tools to discover something new in the subjects that I do care about, like cybersecurity, then I'll pay attention to the results and what they publish in that field.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Jhex@lemmy.world 0 points 7 months ago

No, the actual claims here, that describe specific bugs in specific software, can be evaluated. Even without whipping out a test environment to try to reproduce the results with your own proof of concept, you can read the text and evaluate whether the claims make sense on their face.

Again, why would I bother? I do not work for Anthropic nor any of the other open source projects they are claiming to help so I have not stake in this fight. I am content to ignore whatever wins anthropic claims and wait until those open source projects, whom I do trust more, let me know if these claims are real or not.

I don’t give a shit about AI and I’m generally a skeptic of the future of any of these AI companies. But if someone uses AI tools to discover something new in the subjects that I do care about, like cybersecurity, then I’ll pay attention to the results and what they publish in that field.

Ok, you do you bud... I am happy ignoring Ai until they are proven by third parties... not sure what's so challenging with that notion

permalink

fedilink

source

parent