community_9_modules_atomic_exploit_bridge

modules: atomic_exploit_bridge

Community 9 | 23 files | cohesion 0.33

Definition

This community groups 23 file(s) rooted at modules with dominant language py (cohesion 0.33). Central symbols: AptPlaybook, AptPlaybookEngine, AtomicResolver, AtomicTest, AtomicTestRef, C2Server, C2SessionCommandSet, CalderaAbilityRef. Core file: tests/test_security_hardening_v4.py (67 symbols). Documented purpose: C2 session CommandSet — headless server, agent deploy, exec, loot. Every command is non-interactive and loop-routable: explicit arguments, JSON-able results on.

Files

modules (10 files)

File	Language	Layer	Symbols	Doc
modules/apt_playbooks.py	py	utility	15	yes
modules/atomic_cli.py	py	utility	11	yes
modules/atomic_exploit_bridge.py	py	utility	32	yes
modules/atomic_resolver.py	py	utility	27	yes
modules/c2_agent.py	py	utility	20	yes
modules/c2_surfaces.py	py	utility	11	yes
modules/chain_registry.py	py	utility	10	yes
modules/command_executor.py	py	utility	24	yes

tests (8 files)

File	Language	Layer	Symbols	Doc
tests/test_atomic_exploit_bridge.py	py	testing	36	yes
tests/test_atomic_loop.py	py	testing	17	yes
tests/test_atomic_resolver.py	py	testing	9	yes
tests/test_c2_surfaces.py	py	testing	12	yes
tests/test_chain_registry.py	py	testing	9	yes
tests/test_executor_kernel.py	py	testing	15	yes
tests/test_resource_script.py	py	testing	32	yes

cli/commands (3 files)

File	Language	Layer	Symbols	Doc
cli/commands/c2_session.py	py	utility	10	yes
cli/commands/command_and_control_migrated.py	py	utility	31	yes
cli/commands/resource_scripting.py	py	utility	8	yes

contrib/legacy (1 files)

File	Language	Layer	Symbols	Doc
contrib/legacy/lazydeepseekcli.py	py	presentation	16	yes

core (1 files)

File	Language	Layer	Symbols	Doc
core/safe_exec.py	py	utility	12	yes

... and 3 more files in this community.

Key Symbols

• _lab_auth (function, cli/commands/c2_session.py:24) def _lab_auth() - Return (user, password, https_port, http_port) for the lab C2.
• _fresh_lab_creds (function, cli/commands/c2_session.py:54) def _fresh_lab_creds() - Generate fully random lab operator credentials (no fixed affixes).
• _server (function, cli/commands/c2_session.py:65) def _server(user, password, port) - Build a C2Server bound to lab auth (generates lab creds when needed).
• _issue (function, cli/commands/c2_session.py:83) def _issue(client_id, command, auth, https_port) - POST one command to the C2 issue endpoint (no prompts, ever).
• C2SessionCommandSet (class, cli/commands/c2_session.py:108) class C2SessionCommandSet(LazyOwnCommandSet) - Headless C2 lifecycle + session ops: server, deploy, exec, loot.
• do_c2_server (method, cli/commands/c2_session.py:115) def do_c2_server(self, line) - Manage the headless C2 server (lab use).
• do_c2_reboot (method, cli/commands/c2_session.py:168) def do_c2_reboot(self, line) - Restart the headless C2 server with ROTATED operator credentials.
• do_c2_deploy (method, cli/commands/c2_session.py:251) def do_c2_deploy(self, line) - Deploy the malleable agent to a lab target (needs root shell primitive).
• do_c2_exec (method, cli/commands/c2_session.py:292) def do_c2_exec(self, line) - Run one command on a live C2 session and print its answer.
• do_c2_loot (method, cli/commands/c2_session.py:339) def do_c2_loot(self, line) - Exfiltrate a remote file through a live C2 session into sessions/loot/.
• CommandAndControlMigratedCommandSet (class, cli/commands/command_and_control_migrated.py:39) class CommandAndControlMigratedCommandSet(LazyOwnCommandSet)
• do_msf (method, cli/commands/command_and_control_migrated.py:44) def do_msf(self, line) - Automates various Metasploit tasks including scanning for vulnerabilities, setting up reverse shells
• do_c2 (method, cli/commands/command_and_control_migrated.py:394) def do_c2(self, line) - Handle C2 server setup and agent compilation.
• do_listener (method, cli/commands/command_and_control_migrated.py:516) def do_listener(self, line) - Manage C2 listeners: list, add, start, stop, remove.
• _api (function, cli/commands/command_and_control_migrated.py:543) def _api(method, endpoint, payload)
• do_sandbox (method, cli/commands/command_and_control_migrated.py:644) def do_sandbox(self, line) - Toggle or query Docker sandbox mode.
• do_msfrpc (method, cli/commands/command_and_control_migrated.py:686) def do_msfrpc(self, line) - Connects to the msfrpcd daemon and allows remote control of Metasploit.
• do_sliver_server (method, cli/commands/command_and_control_migrated.py:710) def do_sliver_server(self, line) - Starts the Sliver server and generates a client configuration file for connecting clients.
• do_empire (method, cli/commands/command_and_control_migrated.py:827) def do_empire(self, line) - Generates payloads using PowerShell Empire with various options.
• do_automsf (method, cli/commands/command_and_control_migrated.py:877) def do_automsf(self, line) - Try to check if Vulnerable using the module passed by argument of lazyown example automsf exploit/wi
• do_iis_webdav_upload_asp (method, cli/commands/command_and_control_migrated.py:922) def do_iis_webdav_upload_asp(self, line) - (CVE-2017-7269). Vulnerable using the module iis_webdav_upload_asp of metasploit
• do_duckyspark (method, cli/commands/command_and_control_migrated.py:957) def do_duckyspark(self, line) - duckyspark Compiles and uploads an .ino sketch to a Digispark device using Arduino CLI and Micronucl
• do_emp3r0r (method, cli/commands/command_and_control_migrated.py:1158) def do_emp3r0r(self, line) - Command emp3r0r Downloads and sets up the Emperor server for local exploitation.
• do_atomic_tests (method, cli/commands/command_and_control_migrated.py:1222) def do_atomic_tests(self, line) - Stage an Atomic Red Team test by MITRE technique ID or GUID.
• do_atomic_gen (method, cli/commands/command_and_control_migrated.py:1243) def do_atomic_gen(self, line) - Generate test + cleanup scripts for a MITRE ID or GUID.
• do_atomic_shell (method, cli/commands/command_and_control_migrated.py:1259) def do_atomic_shell(self, line) - Open an interactive root shell on the target when possible.
• do_atomic_clean (method, cli/commands/command_and_control_migrated.py:1289) def do_atomic_clean(self, line) - Clean up engagement artefacts (soft) or tear down the gym (hard).
• do_atomic_emulate (method, cli/commands/command_and_control_migrated.py:1326) def do_atomic_emulate(self, line) - Execute emulation tests on the target through a working shell.
• do_atomic_agent (method, cli/commands/command_and_control_migrated.py:1379) def do_atomic_agent(self, line) - Generates and synchronizes atomic agent scripts.
• do_attack_plan (method, cli/commands/command_and_control_migrated.py:1482) def do_attack_plan(self, line) - Execute a multi-step APT simulation plan.

Internal vs External Edges

• Internal resolved imports (EXTRACTED): 107
• Cross-boundary resolved imports (EXTRACTED): 94

Connections

• [EXTRACTED] depends_on community 0 <-> 9 (strength 0.9): Extracted import edge crosses communities: cli/banner_config.py imports core/safe_exec.py.
• [EXTRACTED] depends_on community 9 <-> 7 (strength 0.9): Extracted import edge crosses communities: cli/commands/command_and_control_migrated.py imports cli/assign.py.
• [EXTRACTED] depends_on community 9 <-> 4 (strength 0.9): Extracted import edge crosses communities: cli/commands/command_and_control_migrated.py imports modules/auto_registry.py.

Risks

• [taint high] cli/banner_config.py -> core/safe_exec.py via subprocess (1 hops)
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/autonomous_exploit_engine.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/autonomous_exploit_engine.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/autonomous_exploit_engine.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/autonomous_exploit_engine.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/atomic_exploit_bridge.py
• [cycle] modules/auto_registry.py -> modules/command_executor.py -> modules/auto_registry.py
• [cycle] modules/auto_registry.py -> modules/command_executor.py -> modules/auto_registry.py
• [layer strict] tests/test_c2_surfaces.py (testing) -> contrib/legacy/lazydeepseekcli.py (presentation)
• [dataflow UNCHECKED_ALLOC] modules/c2_agent.py:162 validate_client_id ct: Result of allocator stored in ct is never checked against NULL.
• [dataflow UNCHECKED_ALLOC] modules/c2_agent.py:212 validate_client_id data: Result of allocator stored in data is never checked against NULL.
• [dataflow UNCHECKED_ALLOC] modules/c2_agent.py:259 validate_client_id _dn: Result of allocator stored in _dn is never checked against NULL.
• [dataflow UNCHECKED_ALLOC] modules/c2_agent.py:606 start log_file: Result of allocator stored in log_file is never checked against NULL.
• [dataflow UNCHECKED_ALLOC] modules/command_executor.py:224 run_tee handle: Result of allocator stored in handle is never checked against NULL.

Open Questions

• Can the cycle modules/atomic_exploit_bridge.py -> modules/lazy_intel.py -> modules/lazy_loop.py -> modules/loop_ai_bridge.py -> skills/hive_mind.py -> skills/lazyown_groq_agents.py -> skills/lazyown_mcp.py -> modules/autonomous_exploit_engine.py be broken with an interface?
• What would break if the most connected file in modules: atomic_exploit_bridge changed?
• Should modules: atomic_exploit_bridge be split, given cohesion 0.33?

Sources

• cli/commands/c2_session.py
• cli/commands/command_and_control_migrated.py
• cli/commands/resource_scripting.py
• contrib/legacy/lazydeepseekcli.py
• core/safe_exec.py
• modules/apt_playbooks.py
• modules/atomic_cli.py
• modules/atomic_exploit_bridge.py
• modules/atomic_resolver.py
• modules/c2_agent.py
• modules/c2_surfaces.py
• modules/chain_registry.py
• modules/command_executor.py
• modules/listener_manager.py
• modules/resource_script.py
• tests/test_atomic_exploit_bridge.py
• tests/test_atomic_loop.py
• tests/test_atomic_resolver.py
• tests/test_c2_surfaces.py
• tests/test_chain_registry.py
• ... and 3 more