Attack Reconstruction

A finished investigation.
Not another alert.

Prophet investigates its own breach signal. It connects network and host evidence, tests competing explanations, and delivers the provenance chain, findings, and next actions for your team to review.

home/detection/investigation
Demo workspace
event triggerProphet
Demo workspace
192.0.2.24Google Drive
volume 512.4 MBsurprise +2.61mismatch 4.60/10score 1
prophetescalate80% confidence
known
An established operator authenticated over SSH, exported internal telemetry to a hidden staging directory, then used rclone to upload about 2.1 GB to Google Drive. The transfer was roughly 1,600× the prior hourly egress level.
unknown
Whether the receiving Google Drive account was approved for this export. The account identity and an authorization record were not present in the collected telemetry.
therefore
Confirm the receiving account and export authorization outside this investigation. If the transfer cannot be tied to an approved task, treat it as a potential unauthorized data export.
overview
hypotheses considered(4)
sub-agents
18143 turns
queries
1562 failed
findings
194 hypotheses
time
12m 14s
provenance chain100% observed

An established operator collected internal telemetry and uploaded it to Google Drive through a detached rclone process.

host analysis-01.demonode node-demo-analysisanchor rclone upload to Google Drive
host value moderate

single-user analysis workstationAccess to an internal search service and an SSH-managed host fleet.

Accessobserved

SSH key authentication from one stable remote source

The session used the established operator account. The collected authentication history showed no failed-login burst or additional source during the reviewed window.

source ip
203.0.113.18single observed remote source
account
ops-demouid 1104
MITRET1133 External Remote ServicesT1078 Valid Accounts
joinsip 203.0.113.18uid 1104
evidence
findinge6847f
Identityobserved

The key belongs to an established human operator

The same key and account appeared consistently on several observed hosts before the transfer. The available records did not establish key theft or a new enrollment.

human
operator@example.testestablished SSH keyholder
MITRET1078 Valid Accounts
joinsip 203.0.113.18uid 1104
evidence
findingcf3a3b
Executionobserved

Python export and rclone resolve to the operator session

Process ancestry connects the export script and detached transfer to the authenticated session. The observed executables were standard Python, shell, and rclone binaries.

process
python3 telemetry_export.pyoperator-launched export script
MITRET1059.004 Command and Scripting Interpreter: Unix Shell
joinsuid 1104ses 318pid 18442
evidence
findingd1e08cfindingbf228a
Collectionobserved

Two exports staged internal telemetry on the workstation

The script wrote about 1.6 GB, then another 400 MB, to newline-delimited files in a hidden temporary directory. The files were local to the host that initiated the upload.

path
/var/tmp/.demo-stage/observations-*.ndjsonlocal staging directory
MITRET1074.001 Data Staged: Local Data Staging
joinsuid 1104ses 319
evidence
findingbf228aderivation40ea9d
Exfiltrationobserved

A detached rclone process uploaded the staged files to Google Drive

Network and process evidence connect the transfer to the staged files and a pre-existing Drive remote. The collected records do not identify the receiving account or establish whether the transfer was authorized.

process
rclone copytopid 18445 · detached, bandwidth-limited transfer
destination
Google Drivereceiving account not established
MITRET1567.002 Exfiltration to Cloud Storage
joinsuid 1104ses 318pid 18445
evidence
finding23aa82findinged9711
discriminatorhigh

Rules out: implant-driven export as the supported explanation

The export was operator-driven, not an observed implant

detail
evidence
findingd1e08c
discriminatorhigh

Rules out: scheduled automation as the supported launch path

No collected record ties the export to a scheduled job

detail
evidence
findingadb85cfindingd1e08c
discriminatormedium

Rules out: an established recurring export in the reviewed period

The sustained upload was not a recurring pattern in the reviewed window

detail
evidence
findinged9711finding677c56

Prior relationship: about 320 KB per hour

Detached rclone transfer begins

About 512 MB per hour; sustained upload across four hours

Communication returns to the prior low-volume range

verify
Google Drive outbound · observed windowSelected transfer flows · four-hour window
corroboratorhigh

Supports: an established operator exported internal telemetry

Local collection, staging, and upload form one observed operation

detail
evidence
findingbf228aderivation40ea9dfinding23aa82

First export writes about 1.6 GB to local staging

rclone starts the upload from the staged files

A second export adds about 400 MB

verify
Upload volume · 15-minute intervals
constraintlow

The workstation provides access and egress, not primary data storage

detail
evidence
findinge8260ederivation9e2611
ambiguity signalhigh

The same operator could perform an approved or unauthorized export

detail
evidence
findingcf3a3bfindinge6847f
ambiguity signalmedium

The Drive remote pre-existed the transfer, but its owner is unknown

detail
evidence
finding23aa82synthesis204f16
enrichment ceilinghigh

Network and host telemetry cannot recover the missing approval

detail
evidence
findingad36cesynthesis204f16
verdict reached↑ see card above
next steps
verdict ceiling

Network and host telemetry establish the export’s provenance. They cannot distinguish an approved operator task from an unauthorized export by the same person when the receiving account and approval record are absent.

what would flip this

An approval record tied to this export and a corporate-controlled receiving account would support a benign disposition. A personal or unsanctioned receiving account, or a confirmed lack of authorization, would support an unauthorized-export finding.

open questions(3)
recommended actions(4)
human review

Review the evidence and record the disposition.

needs review
Completed investigationIllustrative · not live
Illustrative investigationIllustrative reconstruction based on a real investigation. Identifiers and measurements changed; timing condensed. Not live.Anonymized illustration. Not live.

Investigate the signal

Detection is the start of the work. Prophet follows its breach signal through network and host telemetry, gathers evidence, and tests explanations before handing the investigation to your team.

Reconstruct the operation

Trace communication to the initiating process, command, session, and identity. Follow the operation through access, execution, collection, and egress—with observed facts and evidence gaps kept explicit.

Receive the investigation

Review the provenance chain, supporting findings, competing explanations, and recommended actions in one place. Your team receives the investigation, not the work of assembling it.

Make the decision

Prophet states what is known, what remains unknown, and what would change the conclusion. Your team decides whether the activity was authorized and what action to take.

From a network observation to its provenance

Illustrative reconstruction based on a real investigation. Identifiers and measurements changed; timing condensed. Not live.

0s / 40s illustrative sequence

Detection and investigation.
Operated for you.

Deploy Prophet Nodes where traffic is visible. Prophet operates ingest, storage, modeling, and investigation. A TAP or SPAN feed is optional; you do not need to build the central analysis stack.

Deploy
Nodes where you need observation
Receive
Investigations with supporting evidence
Decide
Authorization and response

Give your team the investigation.

Establish observation. Prophet handles the analysis behind it.