ThreatsDay: 296K IoT Botnet, 100+ Water Systems Targeted, SharePoint RCE Chain + 27 New Stories
ThreatsDay: 296K IoT Botnet, 100+ Water Systems Targeted, SharePoint RCE Chain + 27 New Stories. Attackers are now targeting a chain of two Microsoft SharePoint vulnerabilities that can allow them to execute arbitrary code on unpatched servers, according...
What happened
ThreatsDay: 296K IoT Botnet, 100+ Water Systems Targeted, SharePoint RCE Chain + 27 New Stories. Attackers are now targeting a chain of two Microsoft SharePoint vulnerabilities that can allow them to execute arbitrary code on unpatched servers, according to threat intelligence company Defused. The rest of the week gets stranger: botnets borrowing AI, command traffic hiding in public infrastructure, malicious tools waiting before showing their real behavior, exposed systems getting scanned, and exploit windows shrinking again.
Hackers target Microsoft SharePoint RCE chain with PoC exploit.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
A fake productivity app.
Apparently, pretending to be useful is still one of the easier ways into a machine.
The rest of the week gets stranger: botnets borrowing AI, command traffic hiding in public infrastructure, malicious tools waiting before showing their real behavior, exposed systems getting scanned, and exploit windows shrinking again.
ThreatsDay: 296K IoT Botnet, 100+ Water Systems Targeted, SharePoint RCE Chain + 27 New Stories
Attackers are now targeting a chain of two Microsoft SharePoint vulnerabilities that can allow them to execute arbitrary code on unpatched servers, according to threat intelligence company Defused.
Hackers target Microsoft SharePoint RCE chain with PoC exploit
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how influence can become action across an AI agent's tools and permissions.
an AI agent or model consumes instructions, content, messages or context that can influence the next action it chooses.
the system converts that input into one or more intermediate decisions while pursuing the assigned goal.
risk increases when the agent can act outside the model without an independent authorization check.
the effective blast radius is determined by the credentials, data, systems and permissions available to the agent.
a high-impact event becomes possible when an unsafe action is allowed to complete without policy enforcement or human approval.
Why this matters to you
The important lesson is not that every AI agent will behave this way. It is that autonomous systems can combine permissions, tools and intermediate decisions in ways that traditional application controls were not designed to supervise. Your risk depends on what your agents can reach and what stops them before a high-impact action.
Does this deserve attention in my environment?
Check the conditions below against your use of connected AI agents and their tool permissions.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Inventory AI agents that have tool execution, code execution, network access or privileged connectors.
- Require explicit human approval for high-impact actions such as credential use, external writes, security testing or production changes.
- Reduce agent credentials to least privilege and separate evaluation environments from production identities and data.
- Log and review agent-to-agent communication, tool calls and policy denials so unsafe chains are visible.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.