morluto/rea
C2Reverse engineer anything with agents, from app behavior down to native binaries.
★ 100+ · morluto/rea source on GitHub · this plugin in the registry
morluto/rea is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It executes system commands, decodes base64 payloads, starts a network server.
A skill, not an installable plugin — ships SKILL.md with no plugin manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| executes system commands | exec | ×41 in authored code, e.g. scripts/build-conformance-fixtures.mjs:1, scripts/electron-active-hook-boundaries.cjs:356 |
| decodes base64 payloads | base64_decode | ×4 in authored code, e.g. src/application/InterfaceBuilderAnalysis.ts:116, src/application/InterfaceBuilderAnalysis.ts:133 |
| starts a network server | net_server | ×4 in authored code, e.g. src/application/CommandShimReplay.ts:88, src/application/CommandShimReplay.ts:191 |
Outbound domains
www.hopperapp.com
Environment variables it reads
JAVA_HOME HOPPER_LAUNCHER_PATH REA_ILSPY_CMD_PATH npm_execpath REA_VERIFY_SERVER_COMMAND REA_VERIFY_SERVER_ARGS_JSON GHIDRA_INSTALL_DIR REA_READINESS_REPORT_PATH REA_LOG_LEVEL REA_PROCESS_RUN_ID
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.