Operations · Intermediate

Verified

Automated verification

  • Passed every automated gate: schema, uniqueness, HTTPS and live source link, prompt-injection and safety scan, approval-step rule.
  • Drafting model not recorded.
  • Second-model review: kimi-code/k3.1-pro (no critical or high findings).
  • Verified .
  • Automated checks and AI review only, not human review.
How verification works

Triage suspicious traffic against a decoy industrial controller

Classify scans and exploit attempts, then surface noteworthy activity

Use with BotBento

Opens BotBento with this bot ready to create. You check it, create it in one click, then connect its apps. Nothing runs until you do.

  1. When something happensNew decoy event
  2. ThenClassify and record request
  3. ResultDraft triage digest

Monitor a decoy industrial controller and review inbound connection attempts. The bot separates routine crawlers from targeted probes, records request details, groups repeated scans, and highlights attempts that resemble known exploitation patterns. It produces a short digest so a researcher can decide what deserves deeper investigation.

Quick answers

What does it do?

Classify scans and exploit attempts, then surface noteworthy activity. Result: Draft triage digest.

What does it need?

Tools: Terminal, Notes, Chat. Intermediate: some setup. The prompt includes an approval step.

How do I run it?

When something happens: New decoy event. Copy the prompt below into a bot in BotBento.

Prompt to start with

BotBentoRecommended
Read the decoy controller's connection and request records. For each event, note source address, target path, method, headers seen, and whether it resembles a known exploit pattern. Group repeated scanner traffic, keep a running timeline in notes, and draft a concise digest for review. Do not interact with real devices or external hosts. Draft any outbound message and wait for my approval before sending. Do not delete records or make payments.