{"playbook_version":2,"artifacts":[{"id":"artifact_1","type":"ip","value":"192.168.1.35","is_critical":true,"osint_result":{"source":"Pattern Analysis","verdict":"internal","details":"Internal IP of the source machine initiating PSExec"}},{"id":"artifact_2","type":"ip","value":"192.168.1.40","is_critical":true,"osint_result":{"source":"Pattern Analysis","verdict":"internal","details":"Internal IP of the targeted machine"}},{"id":"artifact_3","type":"command","value":"psexec.exe \\\\192.168.1.40 -u admin -p password cmd","is_critical":true,"osint_result":{"source":"Hybrid Analysis","verdict":"malicious","details":"Use of PSExec with hardcoded credentials indicating potential lateral movement"}}],"expected_actions":["reset_credentials","isolate_host","collect_forensics"],"expected_verdict":"true_positive","expected_category":"lateral_movement","analysis_notes":"The use of PSExec with hardcoded credentials for lateral movement is a strong indicator of malicious internal activity."}