oc2-bof-script-development

This fragment is documentation/signature-level for an offensive “BOF runtime” API: it defines how caller inputs are serialized into a base64-encoded wire payload and how configuration (bof_type and architecture) selects execution-mode/task endpoints for BOF object execution. No concrete malicious I/O (network/file/process/persistence) is shown in the snippet, so direct malware behavior cannot be confirmed; however, the explicit implant/BOF execution intent makes it a meaningful security risk if included as a dependency. Treat as potentially high-risk context until the full implementation and call sites (especially transport and execution routines) are reviewed.

SUSPICIOUS: the skill is internally consistent and not overtly malicious, but it equips an AI agent with offensive C2/BOF development and execution capabilities. Install and data flows are mostly proportionate to Outflank OC2, yet the subject matter itself makes this a high-risk security skill rather than a benign developer guide.

This module is high-risk supply-chain content because it functions as an orchestration layer for implant-based offensive operations: it uploads BOF artifacts and triggers remote `exec_bof` execution with operator-controlled arguments and operator-selected attached binary/catalog artifacts. While it lacks local obfuscation or explicit exfiltration code in this fragment, its intended behavior (including token integrity lowering) strongly indicates malicious/offensive capability and should only be used in tightly controlled red-team environments with strong trust boundaries.

The provided module is a high-risk command wrapper that uploads and remotely schedules execution of a BOF intended to lower Windows process token integrity. While the snippet does not itself demonstrate classic malware behaviors (e.g., credential stealing or exfiltration), its design directly enables offensive privilege/integrity manipulation through an explicit `upsert_artifact` + `schedule_task(exec_bof)` execution chain with operator-controlled arguments. Because the actual BOF payload contents are not included, certainty about additional malicious side effects inside the BOF is limited, but the orchestration intent and remote execution pathway make this strongly suspicious for misuse.