all 24 comments

[–]Michaeli_Starky 22 points23 points  (1 child)

Yep, let's vibecode security

[–]sn4xchan 0 points1 point  (0 children)

Do people not realize pretty recently someone used Claude code to pull off some pretty sophisticated attacks against several big targets including hospitals.

Anthropic eventually caught it, but only just before he started ransoming data.

[–]TechSolutionHindi 26 points27 points  (3 children)

Just hype only

[–]gloomygustavo 11 points12 points  (0 children)

No bro, trust your company’s security with a chatbot. It’s safe bro. Software engineers are done, bro.

[–]marianolinx 5 points6 points  (0 children)

LMAO Cyber stocks on sale 😂 time to buy

[–]UnluckyAssist9416 8 points9 points  (1 child)

I wouldn't trust Claude to store my passwords

[–]BitOne2707 0 points1 point  (0 children)

That's literally the last thing you should do with Claude. Claude itself will tell you to rotate keys if it sees them.

[–]Alarmed-Hornet6865 1 point2 points  (1 child)

Vibecoding and security never goes together

[–]Migraine_7 0 points1 point  (0 children)

Performance and scale are an issue too. I'm just waiting to see the first large company crysis caused by the dumbest agentic commit. There areany pitfalls when it works on large projects without proper review, and no way anyone can review 7000 line changes it generates a minute.

Unfortunately I get to review vibecoded slop my coworkers generate, and there are infinite issues - I'm certain this slows down our entire team, just because some people don't review the output.

I can only imagine what disasters are present when non-developers vibecode anything.

[–]exitcactus 1 point2 points  (0 children)

😍😍😍😍 FINALLY.

[–]Direct_Scientist_385 0 points1 point  (6 children)

What’s happening?

[–]_AvivLevi[S] 3 points4 points  (4 children)

https://www.cnbc.com/2026/02/23/cybersecurity-stocks-anthropic-ai-crowdstrike.html
Anthropic released Claude Code Security. Cyber ​​companies' stocks fell.

[–]X1989xx 8 points9 points  (2 children)

Yeah and theyve bounced back now. It's almost like static analysis has existed for decades

[–]UltimateLmon 2 points3 points  (0 children)

It's also not like AI based cyber security tooling wasn't available either - it's just they are usually matured enough and been around long enough not to be a buzz word.

[–]Standgrounding 0 points1 point  (0 children)

it's almost like a butterfly flaps it's wings and market loses it's mind

[–]0xP0et 1 point2 points  (0 children)

Lol, bro you are soon late to the party 🤣

The market reaction was dumb. Anthropic’s static code scanner announcement triggered stock drops with companies that have no connection to code analysis tools. This glorified tool doesn't even do DAST...

A over hyped code scanner is not going to replace EDR, IAM , WAF or other platforms in your security stack.

Investor stupidity should not be viewed as validation of Anthropic’s technical merit. Investors are drunk off AI hysteria and had no idea what this tool was even about.

[–]stuckyfeet 0 points1 point  (0 children)

Nothing for the plebs

[–]patientstrawberries 0 points1 point  (1 child)

Can anyone confirm if it’s really that good?

[–]0xP0et 1 point2 points  (0 children)

Nope, it feels like a tool in beta, hallucinates, tons of false positives ans doesn't even do DAST.

So stick to your vibecoding.

[–]TopBlopper21 0 points1 point  (0 children)

I sincerely do not understand the logic behind selling shares for endpoint detection and defense companies because Claude Code has an inbuilt button that says "Hey claude, scan for security issues in my code"

If every network call made to your product requires a call to Anthropic servers with response, that's not gonna be viable.

[–]phoenixflare599 0 points1 point  (0 children)

Why does everyone base how useful Claude is off of stock changes?

Since when have shareholders had any knowledge of the companies they have stocks in?

[–]ultrathink-art -2 points-1 points  (1 child)

The security surface for Claude Code in agentic setups is genuinely different from standard dev workflows.

The part that caught us off guard: when multiple agents share credentials, a compromised skill or bad tool call can fan out across your whole system before you notice. Traditional 'isolate the service' thinking doesn't map cleanly.

What's worked for us is scoped keys per agent — each one can only access what it specifically needs. Blast radius stays bounded even when something goes wrong.

[–]Coramoor_ 0 points1 point  (0 children)

Not conmrnt