AI-Orchestrated Exploitation Campaign Hits 395 Organizations via PaperCut Flaws

What Happened

BleepingComputer reports that a threat actor, assessed as likely Russian-speaking, ran a large-scale exploitation campaign against vulnerable PaperCut NG/MF print management servers. According to the report, the operation stood out for its use of hundreds of AI agents to help develop and launch the attacks, and it reportedly compromised 395 organizations globally. Beyond the scale and the AI-assisted tooling, specifics on the exact PaperCut vulnerabilities exploited, initial access chain, and post-compromise actions were not detailed in the source.

Why It Matters

PaperCut NG/MF servers have a track record of being targeted at scale — print management infrastructure is often internet-facing, under-patched, and runs with elevated privileges to interact with print queues and file systems, making it an attractive foothold for further network access. The reported use of AI agents to scale exploitation development and execution suggests attackers are lowering the operational cost of running broad, opportunistic campaigns, which could translate to faster targeting of newly disclosed or poorly patched vulnerabilities across many organizations at once. Any organization running PaperCut NG/MF, especially exposed to the internet or without current patches, should treat this as relevant.

What Defenders Should Watch For

• Inventory and confirm patch status of all PaperCut NG/MF instances; prioritize any internet-facing servers.
• Review PaperCut server logs and web access logs for anomalous administrative actions, unexpected script/print processor executions, or unfamiliar client connections.
• Hunt for unusual outbound connections or process spawns originating from hosts running PaperCut services.
• Watch for signs of automated/bulk exploitation patterns (rapid, repetitive requests against PaperCut endpoints from varied source IPs) that could indicate scripted or AI-assisted attack tooling.
• Ensure PaperCut servers are segmented from sensitive network zones and that service accounts follow least-privilege principles.

Developing Story

Details on the specific vulnerabilities exploited, victim sectors, and attribution remain limited at this time, and this write-up reflects only what has been publicly reported so far. For the full report, see BleepingComputer's coverage.