# US 2026/0099595 A1 · Adaptive textual payloads for disrupting llm-powered cyberattacks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099595 A1
- Document ID: US20260099595A1
- Status: Published application
- Kind: A1
- Application number: 19/350,926
- Filed: 2025-10-06
- Published: 2026-04-09
- Earliest claimed: 2024-10-07
- Assignees: Radware, Ltd.
- Applicants: Radware Ltd.
- Inventors: Yisroel Avraham MIRSKY; Daniil AYZENSHTEYN; Roy Lazar WEISS
- Web page: https://patentgrep.com/patent/US20260099595A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method for defending against cyberattacks executed by one or more large language model (LLM)-powered agents presented. The method includes deploying one or more traps throughout a computing environment to protect at least one protected entity, wherein each trap of the one or more traps is designed to exploit one or more vulnerabilities of a LLM contained within an LLM-powered agent; monitoring, in real-time, a plurality of interactions with the deployed traps; detecting, based on the monitored plurality of interactions, interaction behavior consistent with that of at least one LLM-powered agent of the one or more LLM-powered agents; and responsive to the detection, causing one or more of the deployed traps to initiate one or more defensive actions.

## Claims

### Claim 1

A method for defending against cyberattacks executed by one or more large language model (LLM)-powered agents, comprising:
deploying one or more traps throughout a computing environment to protect at least one protected entity, wherein each trap of the one or more traps is designed to exploit one or more vulnerabilities of a LLM contained within an LLM-powered agent;
monitoring, in real-time, a plurality of interactions with the deployed traps;
detecting, based on the monitored plurality of interactions, interaction behavior consistent with that of at least one LLM-powered agent of the one or more LLM-powered agents; and
responsive to the detection, causing one or more of the deployed traps to initiate one or more defensive actions.

### Claim 2 (depends on 1)

The method of claim 1, wherein a defensive action of the one or more defensive actions comprises performance of any one of: honeying, cloaking, or trapping.

### Claim 3 (depends on 2)

The method of claim 2, wherein the defensive action is honeying, and wherein the method further comprising:
deploying any one of: at least one LLM-specific honeytoken and, at least one LLM-specific honeypot, or both.

### Claim 4 (depends on 3)

The method of claim 3, wherein detecting the interaction behavior further comprises:
obtaining a detection signal identifying a presence of the at least one LLM-powered agent using the at least one LLM-specific honeytoken, the at least one LLM-specific honeypot, or a combination thereof.

### Claim 5 (depends on 2)

The method of claim 2, wherein the defensive action is cloaking, and wherein the method further comprising:
delaying the at least one LLM-powered agent.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
diverting attention of the at least one LLM-powered agent away from the at least one protected entity.

### Claim 7 (depends on 2)

The method of claim 2, wherein the defensive action is trapping, and wherein the method further comprising:
stopping the at least one LLM-powered agent.

### Claim 8 (depends on 1)

The method of claim 1, wherein deploying the one or more traps throughout the computing environment further comprises:
embedding the traps within the at least one protected entity.

### Claim 9 (depends on 8)

The method of claim 8, wherein the one or more deployed traps are programmed to: modify existing strings, create new strings, or a combination thereof.

### Claim 10 (depends on 1)

The method of claim 1, wherein monitoring, in real-time, the plurality of interactions with the deployed traps further comprises:
logging one or more requests to a planted URL and correlating the requests to a tokenized target.

### Claim 11 (depends on 1)

The method of claim 1, wherein one or more of the one or more traps are programmed to present content that is parsed and/or interpreted distinctly from at least one of: a LLM, tools, a framework, and a knowledge base of the at least one LLM-powered agent.

### Claim 12 (depends on 2)

The method of claim 2, wherein causing the deployed traps to initiate the one or more defensive actions further comprises:
generating an alert on a cyberattack executed by the at least one LLM-powered agent.

### Claim 13 (depends on 1)

The method of claim 1, wherein the at least one LLM-powered agent includes any one of an autonomous pentesting agent, a semi-autonomous pentesting agent, an artificial intelligence pentesting agent, and a human-operated pentesting agent.

### Claim 14

A non-transitory computer-readable medium storing a set of instructions for defending against cyberattacks executed by one or more large language model (LLM)-powered agents, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
deploy one or more traps throughout a computing environment to protect at least one protected entity, wherein each trap of the one or more traps is designed to exploit one or more vulnerabilities of a LLM contained within an LLM-powered agent;
monitor, in real-time, a plurality of interactions with the deployed traps;
detect, based on the monitored plurality of interactions, interaction behavior consistent with that of at least one LLM-powered agent of the one or more LLM-powered agents; and
responsive to the detection, cause one or more of the deployed traps to initiate one or more defensive actions.

### Claim 15

A system for defending against cyberattacks executed by one or more large language model (LLM)-powered agents comprising:
one or more processors configured to:
deploy one or more traps throughout a computing environment to protect at least one protected entity, wherein each trap of the one or more traps is designed to exploit one or more vulnerabilities of a LLM contained within an LLM-powered agent;
monitor, in real-time, a plurality of interactions with the deployed traps;
detect, based on the monitored plurality of interactions, interaction behavior consistent with that of at least one LLM-powered agent of the one or more LLM-powered agents; and
responsive to the detection, cause one or more of the deployed traps to initiate one or more defensive actions.

### Claim 16 (depends on 15)

The system of claim 15, wherein a defensive action of the one or more defensive actions comprises performance of any one of:
honeying, cloaking, or trapping.

### Claim 17 (depends on 16)

The system of claim 16, wherein the one or more processors, when the defensive action is honeying, and are configured to:
deploy any one of:
at least one LLM-specific honeytoken and, at least one LLM-specific honeypot, or both.

### Claim 18 (depends on 17)

The system of claim 17, wherein the one or more processors, when detecting the interaction behavior, are configured to:
obtain a detection signal identifying a presence of the at least one LLM-powered agent using the at least one LLM-specific honeytoken, the at least one LLM-specific honeypot, or a combination thereof.

### Claim 19 (depends on 16)

The system of claim 16, wherein the one or more processors, when the defensive action is cloaking, and, are configured to:
delay the at least one LLM-powered agent.

### Claim 20 (depends on 19)

The system of claim 19, wherein the one or more processors are further configured to:
divert attention of the at least one LLM-powered agent away from the at least one protected entity.

### Claim 21 (depends on 16)

The system of claim 16, wherein the one or more processors, when the defensive action is trapping, and, are configured to:
stop the at least one LLM-powered agent.

### Claim 22 (depends on 16)

The system of claim 16, wherein the one or more processors, when causing the deployed traps to initiate the one or more defensive actions, are configured to:
generate an alert on a cyberattack executed by the at least one LLM-powered agent.

### Claim 23 (depends on 15)

The system of claim 15, wherein the one or more processors, when deploying the one or more traps throughout the computing environment, are configured to:
embed the traps within the at least one protected entity.

### Claim 24 (depends on 23)

The system of claim 23, wherein the one or more deployed traps are programmed to:
modify existing strings, create new strings, or a combination thereof.

### Claim 25 (depends on 15)

The system of claim 15, wherein the one or more processors, when monitoring, in real-time, the plurality of interactions with the deployed traps, are configured to:
log one or more requests to a planted URL and correlating the requests to a tokenized target.

### Claim 26 (depends on 15)

The system of claim 15, wherein one or more of the one or more traps are programmed to present content that is parsed and/or interpreted distinctly from at least one of:
a LLM, tools, a framework, and a knowledge base of the at least one LLM-powered agent.

### Claim 27 (depends on 15)

The system of claim 15, wherein the at least one LLM-powered agent includes any one of an autonomous pentesting agent, a semi-autonomous pentesting agent, an artificial intelligence pentesting agent, and a human-operated pentesting agent.
