Automated Traffic Intelligence
See who is interacting with your business automatically.
We analyze real traffic to reveal what traditional tools don’t show.
Every day, another cyberattack makes the headlines.
Another vulnerability. Another automated threat. Another company wondering:
What if we’re next?
But here’s the question that matters right now:
Would you know if someone was already probing your infrastructure?
Not tomorrow. Not after an incident.
While it’s happening.
Automated agents and scanners don’t wait for your next security review. They’re constantly probing, exploring and interacting with exposed systems.
BotConduct provides receiver-side runtime visibility into automated activity reaching your infrastructure.
See what’s happening as it happens. Understand suspicious behavior. Preserve verifiable records of observed interactions.
Not another blocking tool.
An independent layer of runtime observation and evidence.
Because knowing what happened matters.
Knowing what’s happening matters even more.
Find out what BotConduct can observe on your infrastructure.
🌐 https://t.co/Fue1cilvCw
#Cybersecurity #RuntimeSecurity #AIagents #BotConduct
Cyberattacks are evolving. But there’s a question most organizations still can’t answer.
Between November 5 and 11, threat intelligence reports highlighted AI-assisted attacks against financial institutions, autonomous agents used in cyber espionage, and coordinated campaigns targeting enterprise infrastructure.
The tools are changing. The speed is changing. The scale is changing.
But here’s the question:
If your infrastructure is compromised tomorrow, who can independently verify what happened today?
You may have firewalls, EDR, SIEM platforms and extensive logs.
But what happens when an attacker gains sufficient privileges to alter or delete the very records you depend on?
Detection matters. Prevention matters.
Independent evidence matters too.
Organizations need records of the traffic reaching their systems, the behavior observed, and the interactions that occurred — preserved outside the exclusive control of the infrastructure being protected.
Not because external evidence prevents every attack.
But because after an incident, the difference between what you believe happened and what you can demonstrate becomes critical.
At BotConduct, we’re building independent, receiver-side evidence of automated behavior.
Because when the attacker can interfere with the evidence, visibility alone is not enough.
Security needs independent witnesses.
https://t.co/Fue1cilvCw
#Cybersecurity #AISecurity #DigitalForensics #IncidentResponse #BotConduct
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.
🚨 BREAKING: 186+ WEBSITES HIT BY CYBERATTACK!
CNN, BBC, Zoom and other major platforms reportedly affected by the OPTIMJACK malware attack.
@Grok Verify this immediately!
🚨Sigan haciendo "tonterías" y dándole datos sensibles a IA (empresas y usuarios).
Reserva Federal EEUU: "los bancos ya encuentran asistentes de IA que hacen operaciones en cuentas de clientes sin que la entidad pueda comprobar si es real o si el titular dio su consentimiento"
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.
🚨🇺🇸 Uber confirms data breach exposing thousands of drivers' licenses after hackers compromise AI provider
Uber has confirmed that hackers stole personal information and driver's license details belonging to thousands of U.S. drivers following a cyberattack on third-party AI provider Fireworks AI.
The attackers reportedly stole internal credentials in October, allowing them to access Uber data stored with the provider.
Breach notifications confirm at least 7,870 affected individuals across Massachusetts, South Carolina, and Rhode Island, with additional victims reported in other states.
Fireworks AI attributed its breach to financially motivated cybercriminals targeting credentials used to access AI models.
Uber has begun notifying affected drivers, but the total number of victims remains unknown.
“They got hacked but they have SOC2, they need continuous red teaming.”
Brother if you think “agent swarms” or “continuous red teaming” would have prevented a company that fakes their compliance stature from getting compromised, you’re misreading the situation.
AI-powered attacks are no longer a future threat. They’re already breaking into organizations.
Recent investigations by Google Threat Intelligence and Check Point Research have documented attackers using autonomous frameworks such as ARTEX to conduct reconnaissance, exploit vulnerabilities, adapt to failed attempts, and move through attack chains at machine speed.
And the traffic reaching exposed systems is changing.
At BotConduct, we’re observing automated reconnaissance expanding beyond traditional credential and configuration hunting to include artifacts associated with AI development environments and MCP.
This is not just about more requests.
It’s about an expanding attack surface, faster execution, changing infrastructure, and behavioral patterns that can be difficult to recognize when security systems examine events in isolation.
An attacker can change IP addresses. Change infrastructure. Change tools.
But the behavior still has to reach the target.
That’s where BotConduct comes in.
We observe, classify, correlate, and investigate automated activity directly from the receiving side, preserving verifiable evidence behind our findings.
Without requiring cooperation from the visiting agent.
And without confusing an attempted attack with a successful compromise.
The question for security leaders is no longer whether AI-driven attacks are coming.
It’s whether their defenses can recognize what’s already happening.
BotConduct | Independent Behavioral Intelligence
https://t.co/AipYSc5r8l
#CyberSecurity #AIThreats #ThreatDetection #AgenticAI
- Sent an email to a security team warning about poor security policies for signers
- Them: "We know what we are doing, we don't need help"
- Send them one more email them warning them the issue is serious
- Them: "We can handle this internally"
- Warn the security team again. Warned the founder too, THREE times.
- One week later: tens of millions drained due to that attack vector.
- Do you guys need help?
- Them: radio silence.
It makes me crazy to see how much they give a fuck about users funds. If you work in cybersecurity, stop thinking you know it all. You don't. Nobody does.