41XMXQfkqKMvcZYwXorX2HDto5h6sc1rKxEF1WYTyIgsTaKCett8CDf8ftYq66dO0qzglntw3StdHlfvXn6tUilhHubYOHD — IoC

CASE-20260810-0507 MEDIUM OPEN Assignee: unassigned · Opened 13h ago

Opened from ioc 41XMXQfkqKMvcZYwXorX2HDto5h6sc1rKxEF1WYTyIgsTaKCett8CDf8ftYq66dO0qzglntw3StdHlfvXn6tUilhHubYOHD

🔄 Pivot:📁 ioc

Entities

linked to case

IoCs

indicators

Entity types

dimensions

Evidence events

chain of custody

➕ Add anything to this case

Attach any entity — region, country, APT, source, MITRE technique, IoC, nation-state, campaign, data point, mission domain, CVE, malware, ransomware — and all linked entities are pulled in automatically.

🔎 IoC (1)

Indicator	Role	Source
`41XMXQfkqKMvcZYwXorX2HDto5h6sc1rKxEF1WYTyIgsTaKCett8CDf8ftYq`	primary	manual	search · workbench

🤖 Case Operations

AI Copilot brief AI Skills Skills Library Playbooks Playbook Library Workstations Automations Correlation graph Data Points Sources Export STIX/MISP Evidence report Watchlist Report

📜 Chain of Evidence (tamper-evident, hash-chained)

When	Actor	Action	Entity	Source	Hash
2026-08-10 08:09:40	analyst	add	ioc: `41XMXQfkqKMvcZYwXorX2HDto5h6sc`	manual · primary	`da35c82bc1`
2026-08-10 08:09:40	analyst	open	ioc: `41XMXQfkqKMvcZYwXorX2HDto5h6sc`	analyst · case created	`ff8c64227a`

Each record's hash chains to the previous, so any tampering is detectable. Export the full trail via the Evidence report.

📝 Case Notes (0)

← All Cases

Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports

🤖 AI Copilot

💡 Recommendations

⚙ Automation

Escalate from triage

Cron: 0 * * * * php /home/zaptf0zdggll/public_html/threats/cron.php

📜 Playbook

Open Response Playbook

🔗 Related Tools

Legal & LE Playbooks Reports

Case Management