upvote

points

by glimshe1 days ago |
comments
upvoteby _heimdall1 days ago|
next
[-]
Don't worry, I assume an LLM version of McAfee Total Protection Antivirus is coming soon
reply
upvoteby nannal1 days ago|
parent|
next
[-]
I do have a log reading / action / resolution product in the works.

Its sort of like having a sysadmin constantly watching. Poking through logs pcaps & monitoring for unusual activities.

Also works with local models well enough.

reply
upvoteby jmbwell23 hours ago|
parent|
next
[-]
I love how LLMs have brought DIY software back. Need an app? Just make it. Like back when you’d write programs in BASIC
reply
upvoteby codazoda23 hours ago|
parent|
next
[-]
I just built a retro OS for ESP32’s so that I can write BASIC programs and plop them on microcontrollers. My first ESP32 was a wrist watch. My second is a distraction free writer.

It’s good fun building for retro-like machines.

reply
upvoteby stogot23 hours ago|
parent|
prev|
[-]
This is where I silently found gold. All those old TODO when if I have time in retirement
reply
upvoteby nannal22 hours ago|
parent|
[-]
I've got a whole heap of unfinished side projects that I'm digging through
reply
upvoteby InsidiousWombat22 hours ago|
parent|
prev|
next
[-]
That's cute but bill for going thru even tens of log lines per second gonna be more expensive than entire rest of the infrastructure.
reply
upvoteby nannal10 hours ago|
parent|
[-]
You don't have to use frontier for this & all my agentic work is local only.
reply
upvoteby saagarjha2 hours ago|
parent|
[-]
You may have trouble catching good attempts then.
reply
upvoteby Filligree1 days ago|
parent|
prev|
next
[-]
I’ve set up something like that with Opus. Works well enough, and points out CVEs to fix on the regular.

Running NixOS helps.

reply
upvoteby Geezus_421 days ago|
parent|
prev|
next
[-]
I've set up something like that with a small local model in my homelab.
reply
upvoteby cedws21 hours ago|
parent|
prev|
[-]
How does it resolve the prompt injection?
reply
upvoteby jacquesm22 hours ago|
parent|
prev|
[-]
And if you remove it, it installs itself right back. For uninstall instructions see the infamous McAfee video.
reply
upvoteby viraptor23 hours ago|
prev|
next
[-]
This is a cheap troll, but just in case someone is wondering: This extension likely never hit the standard workflow and/or repository. Most likely someone got the credentials and uploaded a locally modified version. No review system at anthropic has seen this version.
reply
upvoteby eviks22 hours ago|
parent|
next
[-]
Why wouldn't their review system see a published extension and determine the very second it's published that it didn't match the results of a standard workflow?
reply
upvoteby crooked-v16 hours ago|
parent|
next
[-]
Because it wasn't published by them or hosted on a system they control, it was done directly on Cursor's mirror of OpenVSX with a modified copy of the original extension.
reply
upvoteby 18 hours ago|
parent|
prev|
[-]
deleted
reply
upvoteby cryptonym23 hours ago|
parent|
prev|
next
[-]
> someone got the credentials

> No review system at anthropic has seen this

Weird flex

reply
upvoteby viraptor22 hours ago|
parent|
[-]
I'm not sure where you see the flex. If someone gets hold of the token allowing the upload of your app to the store, it's completely irrelevant how good your internal code/review systems are. They've been completely bypassed and never triggered.
reply
upvoteby cryptonym22 hours ago|
parent|
next
[-]
Arguably, your security shouldn't stop at internal code review and should aim at protecting key distribution platforms credentials and assets that are pushed to your users.
reply
upvoteby viraptor22 hours ago|
parent|
next
[-]
Yeah, it shouldn't. But at that point it's not "Why didn't Claude detect the hack" but rather "Why isn't Claude running all processes at your company autonomously", which is a bit silly. We know it isn't and it's not at that level, because anthropic employs engineers.
reply
upvoteby cryptonym22 hours ago|
parent|
prev|
[-]
> at that point it's not "Why didn't Claude detect the hack" but rather "Why isn't Claude running all processes at your company autonomously", which is a bit silly.

Would be nice to have some words from them understanding how they manage this, what went wrong, how they'll prevent this in the future. We don't have any RCA, maybe there is little to nothing to blame them.

Not sure they'd share your views on using Claude for security policy/coverage being silly.

reply
upvoteby unshavedyak22 hours ago|
parent|
prev|
[-]
As an aside, it would be neat if publishing services like this had a sort of 2FA, eg the package manager had a hook endpoint where it sent the details of the next requested published version. Allowing the owners to validate.

Kinda like 2FA on the deployment itself, not just 2FA on the .. A. I guess 2FD heh.

reply
upvoteby InsidiousWombat22 hours ago|
parent|
prev|
next
[-]
It's legitimate question, it's the promise they are selling and doing IPO based off those promises.

Why don't they have their super intelligence looking thru it? If company selling those promises can't even do it for themselves, this is very suspicious

reply
upvoteby paxy22 hours ago|
parent|
[-]
Who is "they"? This is a third party registry.
reply
upvoteby jacquesm22 hours ago|
parent|
prev|
[-]
Intelligence that powerful and for them too cheap to meter and their review system couldn't be bothered.

That wasn't a cheap troll. What they distribute and what Claude Code installs is on them. You're supposed to keep your channels clean and secure.

At a minimum they should monitor the larger marketplaces even if they're not in the chain.

reply
upvoteby MisterTea1 days ago|
prev|
next
[-]
They weren't using last minutes model, which is totally better than last hours model which would have totally detected this, pinkie swear.
reply
upvoteby vintermann22 hours ago|
parent|
next
[-]
Having Claude examine all automatic software updates was considered as a policy, and it was found that it would stop 99.5% of software supply chain attacks. However the other 0.5% of the time it would install a backdoor itself.

(This is a joke, to be clear.)

reply
upvoteby ben_w22 hours ago|
parent|
next
[-]
> (This is a joke, to be clear.)

Good that you said so, this is annoyingly plausible.

reply
upvoteby bagacrap22 hours ago|
parent|
prev|
[-]
Somehow bullish if anthropic spins this as Claude's own doing
reply
upvoteby claytongulick23 hours ago|
parent|
prev|
[-]
Damn, thank you for that.

Sums up my feelings of the last few years nicely.

reply
upvoteby eviks1 days ago|
prev|
next
[-]
It was safety-contrained from being able to realize its full potential.
reply
upvoteby 13 hours ago|
prev|
next
[-]
deleted
reply
upvoteby Hackbraten1 days ago|
prev|
[-]
You’re absolutely correct, and I owe you a honest statement—it was a hack, and here’s the kicker: *I failed to catch it, and that’s on me.*

Here’s a complete rundown of what happened—load-bearing parts first:

reply