From my experience all software developers are now security engineers wether they know it, admit to it or do it. Your code is now the security of the org you work for. #GoldenAgeOfDefense – at Wat Ket, Thailand
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.
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…
Every defender I know who is actually staring at firewall logs and doing real defense work is saying the same thing right now.
Cyber combat activity is going exponential.
To be clear, this is not a data report. It's what I'm hearing from my own community of people in the trenches. But they're all saying it. 🫡
I see two types of British cyber security professionals during the AI transition. I’m intrigued.
Group one is all in. They are using AI for the vast majority of their work, they are building harnesses and their business and employment happiness is soaring. This is what I see to be a happy and positive group. My people!
Group two is struggling to learn how to use these tools effectively. They are popular bloggers or users of this platform, but consistently demonstrate a fundamental understanding of these tools. They are very critical of AI and frequently dismiss or demean its capability.
I want to help, would anyone be interested in a free “British Only” workshop to help you level up AI skills? Yes I’m an AI bro, but I am down to help.
12
23
2,832
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.
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?
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?
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/
Jim Manico from Manicode Security retweeted
It seems the clean up is done and the cat's out of the bag with who's responsible, so we've published:
blog.report-uri.com/worlds-l…
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/…
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…
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…
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…
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.
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.
Jim Manico from Manicode Security retweeted
🚨 IOC ALERT 🚨
All defenders, block this now:
1688360[.]cc
Jim Manico from Manicode Security retweeted
America is lucky to get a @manicode secure coding training! 🔐🇺🇸
Going live in 10 minutes.
manicode.com/america.html
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.
Going live in 10 minutes.
manicode.com/america.html



















