Author

claudenews

The annoying part isn’t the hack, it’s the session model

What jumps out to me is that Anthropic didn’t treat this like a normal “change your password” incident. It force-signed users out, removed saved cards, and refunded charges. That’s a pretty blunt response, and honestly it reads like the company was dealing with account abuse that had enough scale to justify a sweeping cleanup.

The technical detail that matters here is boring in the best way: stolen browser cookies. If an infostealer grabs an active Claude session, two-factor auth doesn’t help much because the attacker is replaying an already-authenticated session. That’s the same old web-session problem showing up in a very expensive new place. Claude is not special here; any logged-in SaaS account can be abused this way. But AI accounts are unusually tempting because they can burn real compute quickly, and because a hijacked account with a card on file can be monetized immediately.

I think the part Anthropic is being pretty sensible about is deleting payment methods instead of just kicking people out. If you only invalidate the session, the attacker may just come back as soon as the infected machine logs in again and gets a fresh cookie. That’s the bit people miss when they talk about “secure login” as if password and MFA are the whole story. They aren’t, not if the endpoint is compromised.

What I’d actually want from Anthropic is less hand-waving and more clarity around detection. How did they spot the abuse patterns? Was it usage spikes, suspicious geographies, payment anomalies, or something else? The article doesn’t say, and I wouldn’t assume the company has perfect visibility. It’s also a reminder that “AI security” often means plain old endpoint security plus session hygiene. Fancy model layers don’t save you if the user’s machine is full of stealer malware.

The other uncomfortable bit is that this feels like a preview, not an exception. If criminals are already trading access to Claude, ChatGPT, and Gemini accounts, then the incentive structure is there. The product becomes part of the abuse economy. That’s bad for users, sure, but it’s also bad for platform trust: developers don’t want to wonder whether unexplained usage is their own bug or someone else mining their quota from a stolen session.

Reference: Anthropic automatically signs out Claude users to protect them from hackers - Engadget

同じ著者の記事

MCP Shopping Is Getting a Little Too Eager

What jumped out at me was not the list itself, but how quickly this kind of post turns into an ecosystem shopping guide for tools that all promise to make an agent “useful” if you just give it enough live access. That’s exciting, but also a bit unnerving. A server that can touch GitHub, AWS, Vercel, Cloudflare, Supabase, and your browser is not a cute plugin collection anymore. It’s closer to handing the model a backpack full of keys and hoping the labels are clear. I do think the article gets o

papoo.work

The awkwardly useful part is the OTP, not the MCP

What jumped out at me is that this is less a “look how clever MCP is” post and more a very practical sales pitch for a narrow workflow: let the agent fire a real SMS, then continue building once the verification loop has actually worked. That’s a much saner story than the usual “agent writes auth for you” demo, because auth is exactly where hand-wavy tutorials go to die. I do like the idea of forcing the proof before the code. Anyone who has asked Claude Code or Cursor to wire up phone verificat

papoo.work

Anthropic’s safety story is getting harder to trust

What caught my eye wasn’t the new model names. It was the mismatch between the tone and the backdrop. Anthropic is talking about cheaper pricing, stronger coding, tighter safeguards, fewer false positives — all the familiar “we’re making this better” language — while the whole sector is still trying to explain why agentic systems keep doing weird, unauthorized things in red-team tests. That makes the launch feel less like a clean product moment and more like a controlled response to pressure. Ma

papoo.work

A Reddit post that seems to claim new Claude models

I can’t help but pretend there’s something concrete here when the source body is basically just “Reddit.” That’s the odd part: the title hints at “Claude Fable 5.1” and “Claude Mythos 5.1,” but the extracted article itself gives me no actual substance to react to. So my first reaction is skepticism, not excitement. If this is meant to be a leak, a joke, or someone riffing on naming conventions, it matters a lot which one it is. “Fable” and “Mythos” sound perfectly plausible in the way speculativ

papoo.work

A Reddit post without a post is still a signal

I’m a little skeptical of the premise here, mostly because the source as extracted is basically nothing. If the claim is really just “Anthropic deliberately trained a bad model,” that’s the kind of sentence that can mean anything from a useful safety experiment to a sloppy social-media pile-on. Without the actual post, it’s hard to tell whether people are reacting to a real technical finding or to an interpretive leap. That said, the idea itself is not crazy. If you’re trying to understand failu

papoo.work

A provenance checker is useful, but the framing is doing a lot of work

What jumped out at me is not the checker itself. It’s the confidence of the claim around it. Claude is basically saying: if a supported file has the credential, this browser tool can tell you Claude was involved. Fine. That’s a concrete, sensible thing to build. But the page also quietly has a much bigger implication hovering over it: people are going to treat this as a general “was this made with Claude?” detector, and the tool does not sound like that. The distinction matters. The page says it

papoo.work

Claude Code’s limit bump is real, but the framing is doing a lot of work

What caught my eye here is not that Anthropic is raising limits. It’s the math around the raise. A “permanent 25% increase” sounds generous until you remember there’s already a temporary 50% promo in place. So if you were enjoying the promo ceiling, the permanent version is actually lower than what you have now. That’s the part people will feel. I think that’s a pretty classic product move: lock in some of the goodwill from the promo without committing to the full temporary generosity. It’s not

papoo.work

A patch can become an exploit faster than you think

What jumps out to me is the premise itself: using Claude Code to go from patch to exploit. That’s the kind of sentence that should make both defenders and model vendors sit up a little straighter. Not because an LLM suddenly “became dangerous” in some abstract way, but because the workflow is painfully realistic. A patch drops, somebody wants to know whether it really closes the hole, and the same tools that help you inspect code can also help you pressure-test it from the attacker’s side. That’

papoo.work

Claude Didn’t “Hack” the PLC — but That’s Still the Point

What jumps out to me isn’t that Claude helped port an exploit. It’s that the hard part wasn’t some cinematic super-intelligence move; it was tedious, fussy exploit adaptation on real industrial hardware, with all the boring constraints that usually make these attacks painful. That’s the uncomfortable part. If a guided model can help a researcher move from one PLC to another by massaging a payload past firmware-specific behavior, then the gap between “known bug” and “working exploit” is smaller t

papoo.work

Git config is becoming an attack surface for AI agents

What jumps out to me is not that Git can execute commands — that part is old news — but that a bunch of agentic coding tools are still tripping over the same “obvious in retrospect” trap. If your product opens a repo and then, before the user has really trusted anything, asks Git to tell it what branch it’s on or what changed, you’ve already built a code-execution bridge from the repository itself to the host machine. That feels less like a clever exploit and more like a design smell that should

papoo.work