Jim Manico from Manicode Security (@manicode) header
Jim Manico from Manicode Security (@manicode) profile picture

18th-Level AI Magic User 🧙‍♂️ Teaching developers to build secure software with AI https://nitter.cf/t.co/p2rffkkHbC

Kauai, HI and Cobb, CA
Joined July 2009
Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)Photo by Jim Manico from Manicode Security (@manicode)
Jim Manico from Manicode Security retweeted
Replying to @manicode
Can confirm from my talks with CISO's I advise. They all feel like they are in a constant state of incident response.
1
1
5
477
Jim Manico from Manicode Security retweeted
I was working through this today with @Scott_Helme, and it’s MASSIVE! Most sites would have absolutely no idea their customers were being served malware. Where do you even begin with disclosure on that one?!
This is a big one. We found malicious JavaScript being served through Optimizely to some of the world's largest websites. 178 organisations affected, with everything from crypto theft and card skimming to iOS exploits. Zoom, BBC, CNN, HSBC, Salesforce, GitLab, KLM, IKEA, Equifax, Ledger. The list goes on... Full list in the post. blog.report-uri.com/worlds-l…
31
70
2
518
52,903
Jim Manico from Manicode Security retweeted
The only model better than Opus 5.5 is Opus 5.5 that calls Fable 5.2 at the right times.
7
4
4
61
5,702
Jim Manico from Manicode Security retweeted
Crazy day in security 1. @Chase, @BankofAmerica, @WellsFargo and @Zelle went down. They claim it's not a hack or security incident. Downtime will have huge downstream economic impact. 2. @Optimizely scripts were poisoned on 178+ sites: @Zoom, @BBC, @CNN, HSBC and more. Visitors were served malware. 3. @united had an outage and held flights. Root cause is unknown. 4. @Google reports the first fully automated patch-to-exploit pipeline. AI agents are now running attacks end to end. Will every day from now look like this?
27
76
17
585
89,610
Jim Manico from Manicode Security retweeted
Not bad for some overhyped autocomplete.
Crazy day in security 1. @Chase, @BankofAmerica, @WellsFargo and @Zelle went down. They claim it's not a hack or security incident. Downtime will have huge downstream economic impact. 2. @Optimizely scripts were poisoned on 178+ sites: @Zoom, @BBC, @CNN, HSBC and more. Visitors were served malware. 3. @united had an outage and held flights. Root cause is unknown. 4. @Google reports the first fully automated patch-to-exploit pipeline. AI agents are now running attacks end to end. Will every day from now look like this?
2
1
1
17
4,686
Jim Manico from Manicode Security retweeted
AI Security Engineers work at the intersection of software engineering, security engineering, and AI engineering to secure AI-native systems throughout their lifecycle. Check out Jobs for AI Security Engineers. aiseceng.io/
1
2
189
Jim Manico from Manicode Security retweeted
It's remarkable to me that so many people in security didn't believe this would happen. As I've been saying: most of offensive security is extremely tedious plumbing and accounting. And AI is really good at automating all of that. theregister.com/cyber-crime/…
7
4
1
39
5,018
Jim Manico from Manicode Security retweeted
incredible talk by @poteto on how to ship quality, not slop: build trust in your own tooling via automated verification. spend more tokens on verification (rather than generation). youtube.com/watch?v=O_zcc6Xl…
6
8
2
221
12,192
Jim Manico from Manicode Security retweeted
This is a big one. We found malicious JavaScript being served through Optimizely to some of the world's largest websites. 178 organisations affected, with everything from crypto theft and card skimming to iOS exploits. Zoom, BBC, CNN, HSBC, Salesforce, GitLab, KLM, IKEA, Equifax, Ledger. The list goes on... Full list in the post. blog.report-uri.com/worlds-l…
136
1,117
196
3,116
449,994
Jim Manico from Manicode Security retweeted
I'm genuinely really excited about this feature! It's the result of some hard work and I can see it providing some mega value. It's a short blog post, and I'd love some feedback from you! blog.report-uri.com/introduc…
2
5
2
19
21,845
Jim Manico from Manicode Security retweeted
"We’re facing a different class of offensive technology, and I think many people still haven’t understood that."
I think there’s a fundamental misconception in how the security industry talks about ARTEX, Cairn and similar offensive AI frameworks. And even reports from major security vendors keep reinforcing it. People treat these frameworks like the C2 frameworks we’ve known for years. With Cobalt Strike and others, parts of the framework were deployed on the victim’s systems. Implants, loaders, communication protocols and other implementation details provided recognizable patterns that we could write signatures for. But ARTEX and Cairn work differently. The orchestration runs on the attacker side. The LLMs, prompts, skills, tools and infrastructure are interchangeable. Change any of these components and the resulting attack can look completely different. The framework itself doesn’t define what ends up on the victim’s systems. Yes, there are a few minor implementation fingerprints, such as certain ARTEX/Norma User-Agent strings. We’ve even written rules for them. But these cover tiny parts of a framework’s functionality, not the attacks it can orchestrate. An IP address, webshell or exploit used in a campaign doesn’t suddenly become an “ARTEX indicator” because ARTEX was involved. And that’s why I find all these “ARTEX IoC collections” and “How to detect ARTEX” guides so misleading. They encourage people to think we’re dealing with another recognizable malware or C2 framework. We’re facing a different class of offensive technology, and I think many people still haven’t understood that. The detection guidance should be what we’ve been telling defenders for decades: detect malicious behavior, attack techniques and traces of compromise. There is no special defense against ARTEX. Tomorrow the same attacker could use a different framework, a different model and completely different tools. The names are disposable. The underlying attack techniques are what we need to detect.
6
30
4,847
Jim Manico from Manicode Security retweeted
We are tracking a breach of a 3rd-party JS host impacting hundreds of high value websites. This is staggering.
267
1,793
310
12,746
2,874,979
Jim Manico from Manicode Security retweeted
🚨 IOC ALERT 🚨 All defenders, block this now: 1688360[.]cc
9
107
7
646
386,914
Jim Manico from Manicode Security retweeted
My point is that AI has raised the floor, but it's also raised the ceiling. People with actual skills and experience are more capable than ever.
The current state of AI is such that you could give five people in offensive security, all with varying skill levels, access to Codex or Claude and the exact same codebase or network to target, and get five very different results.
10
13
6
178
8,955
Jim Manico from Manicode Security retweeted
This makes sense, but when was the last time a company changed its core working principles to improve its security posture( Maybe Microsoft's post-Gates memo)? Security culture is downstream of org culture, not the other way around. I don't expect companies to become AI-native to improve Security
When you figure out why “just patch” is shitty advice to give to any significant sized company you’ll also know why AI will benefit attackers far more than defenders. In bigger orgs the problem is not usually a lack of tech, or models, or skills on the security team. It’s that there is a level of organizational friction at every company, like a friction coefficient, that stops security orgs from being able to do many things they want. We’ve needed asset management for decades. We’ve needed mappings between code and apps and servers and dev teams and developers forever. Very few have these. The tech exists. The problem is the org is not set up to build and maintain these types of systems continuously. The company’s structure itself, built around opaque silos, and divergent goals, and insanely lossy and inefficient communication across the company, it all creates a very high friction coefficient for basically any fast improvements. The way to fix security is to lower this friction coefficient inside companies. It sucks to hear, but we’re at the point of security’s biggest issue being the company itself. The org structure. The old way of managing teams and goals and work. An AI-native org is the only way to get organizational friction down to a level that can compete with these new attacks and attackers. The bad news is this is big. And it’ll be difficult for a lot of people to adjust to. And a lot of people currently working there won’t be needed in the new model. The good news is many still will, and even more could be needed once the efficiency of the new organization kicks in. This isn’t just going to help addition; it’ll help the entire business move faster. Going into 2027, I believe this model is about to move from ideal and experimental to … essential. Both for surviving cyber-wise, and as a company facing increased and up-leveled competition.
1
4
458
Jim Manico from Manicode Security retweeted
Replying to @manicode
That’s exactly it, and it is those compensating controls I’m interested in. “Sloppy” and “IT” is redundant too, it’s a reality we will always have to work with. Vast majority of orgs haven’t gotten to a maturity level beyond this.
1
1
1
331
Jim Manico from Manicode Security retweeted
As on of the OGs on this topic, it is so nuanced. Patch everything all the time small microservices with great test coverage... large legacy, patch reachable/exploitable as fast as you can. Patch/upgrade everything else as you can - Ideally removing 3rd party libs where you can.
* 2020 AppSec: "Why aren't you patching everything?!"
* 2026 AppSec: "Whoa whoa, stop patching everything. Risk-based approach please." Some of us OGs will complain no matter what. I say this as one of them. 🫡
2
1
3
344