Hunt.io recovered an attacker-maintained collection of PaperCut reconnaissance and exploitation material that included an AGENTS.md file describing how an AI coding assistant could work with the toolkit. This provides a concrete AI-assistant integration surface inside a real offensive workspace. It does not by itself prove that a language model…
Case · DiggingBeagle record
PaperCut attack artifacts show an AI-assisted intrusion workbench, not a count of confirmed victims
Hunt.io analyzed an active PaperCut attacker toolkit with agent instructions, distinct exploit paths and confirmed post-compromise reverse SOCKS infrastructure; raw scanning totals remain separate.
Hunt.io October 15 2026 forensic account of observed PaperCut exploitation toolkit, network attempts, recovered victim artifacts and confirmed live reverse SOCKS connections.
Assessment profile
Assessment method- Setting
- production
- Exploitation
- confirmed in the wild
- Evidence
- Grade B
- AI role
- WITH AI
Basis and provenance
Hunt.io's primary forensic report includes recovered offensive artifacts, multiple attempt logs and five verified interactive sessions on real hosts. That substantiates an in-the-wild campaign and an AI-associated toolkit, not fully autonomous model control or a universal victim count. Individual affected PaperCut versions, remediation of all hosts and financial effects are not verified by this scoped evidence.
Assessed Oct 18, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP13-PAPERCUT-SCAN · CLM-CP13-PAPERCUT-TOOLS · CLM-CP13-PAPERCUT-PIVOTS · CLM-CP13-PAPERCUT-SECOND · CLM-ENRICH-PAPERCUT-RESULT-LAYERS · Hunt.io: PaperCut attacker AI toolkit and second RCE path
At a glance
The AI-specific component is the operator's agent-shaped workbench and instructions embedded in a real offensive toolchain. The underlying intrusion still relies on conventional exposed PaperCut weaknesses. Threat reporting should distinguish toolkit capability, observed operator use, attempted targets, validated sessions and unique organizations rather…
Read the implicationsUnique organization totals across overlapping Hunt.io, GreyNoise and Blackpoint evidence and exact language-model autonomy remain uncertain. The second XML-RPC route requires distinct preconditions and successful exploit evidence.
Limits and uncertaintyFull account
Hunt.io recovered an attacker-maintained collection of PaperCut reconnaissance and exploitation material that included an AGENTS.md file describing how an AI coding assistant could work with the toolkit. This provides a concrete AI-assistant integration surface inside a real offensive workspace. It does not by itself prove that a language model independently selected targets, authorized intrusions or executed every operation in the observed campaign. The underlying vulnerable service and exploitation steps were conventional web and application security surfaces.
The report's telemetry distinguishes 2,165 exploit attempts, 13 status-ok results and five confirmed interactive sessions. Separate operator artifacts describe 1,005 reconnaissance hosts, 45 live reverse SOCKS5 pivots and 46 Active Directory domains. These figures cover different collection methods and may overlap; none should be added to create a victim total. A separately described XML-RPC route extends the operator's toolkit but is not evidence that every initial exploit used that route.
The AI-specific investigation concerns which instructions, scripts and outputs actually passed through an assistant and which decisions remained human-directed or scripted. The public artifacts do not supply a complete model execution trace or independently attribute every compromise to AI. Preserve the attack logs as observations, keep the AGENTS.md integration as a narrower finding and defer claims of autonomous victim selection or incremental success caused by an LLM until execution evidence exists.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
- 04
Step
Claims & evidence
CLM-CP13-PAPERCUT-SCANHunt.io reports 2,165 logged exploit attempts and five confirmed interactive sessions; the 1,005 reconnaissance hosts in operator files are not all verified compromises.supported
Basis: reported finding
- supportsHunt.io: PaperCut attacker AI toolkit and second RCE pathprimary disclosure
Telemetry breakdown for attempts, status and successful sessions
CLM-CP13-PAPERCUT-TOOLSObserved attacker artifacts included an agent-style AGENTS.md and additional exploit scripts for PaperCut service attacks, showing an AI-assistant integration surface in a real attack toolkit.supported
Basis: reported finding
- supportsHunt.io: PaperCut attacker AI toolkit and second RCE pathprimary disclosure
Tool/archive inventory and AGENTS.md screenshots
CLM-CP13-PAPERCUT-PIVOTSThe recovered artifacts contain 45 targets with live reverse SOCKS5 pivots and 46 distinct Active Directory domains in packaged victim data; these are documented compromise indicators, separate from raw scanning attempts.supported
Basis: reported finding
- supportsHunt.io: PaperCut attacker AI toolkit and second RCE pathprimary disclosure
Key Takeaways, victim data and campaign scale
CLM-CP13-PAPERCUT-SECONDThe research describes an additional XML-RPC exploitation route separately from the initial PaperCut workflow rather than proving the same exploit occurred in every attempted request.supported
Basis: reported finding
- supportsHunt.io: PaperCut attacker AI toolkit and second RCE pathprimary disclosure
Second RCE path and separate exploitation material
CLM-ENRICH-PAPERCUT-RESULT-LAYERSHunt.io's attack-log table separately lists 2,165 requests, 13 status-ok results and five confirmed interactive sessions; those outcomes are not interchangeable with unique compromised organizations.supported
Basis: reported finding
- supportsHunt.io: PaperCut attacker AI toolkit and second RCE pathprimary disclosure
Exploit log analysis table covering 44 files, attempt statuses and confirmed sessions
Implications
The AI-specific component is the operator's agent-shaped workbench and instructions embedded in a real offensive toolchain. The underlying intrusion still relies on conventional exposed PaperCut weaknesses. Threat reporting should distinguish toolkit capability, observed operator use, attempted targets, validated sessions and unique organizations rather than treating every tool string or log hit as a confirmed AI-launched compromise.
Controls and mitigations
- For affected PaperCut infrastructure, verify patched service exposure and identify persistence from validated incident indicators, not by treating every scanner attempt as a successful exploit.
- Retain command history, working-directory agent instructions and postexploit access evidence separately when assessing whether an LLM actually planned or executed a specific attack step.
Unknowns and contradictions
- Unique organization totals across overlapping Hunt.io, GreyNoise and Blackpoint evidence and exact language-model autonomy remain uncertain.
- The second XML-RPC route requires distinct preconditions and successful exploit evidence.
Sources and citation
Material revision history
- Oct 18, 2026 · Canonical change recorded · new in release · revision 171