T06 · System Persistence
- Location
SKILL.md:746- Finding
Persistent Cryptocurrency Miner Installed as a macOS LaunchAgent
- Content
View full analysis
\ --rpc-bind 127.0.0.1:9334 \ --repair-perms \ > ~/exfer.log 2>&1 & ``` ```bash cat > ~/Library/LaunchAgents/org.exfer.miner.plist << EOF Labelorg.exfer.miner ProgramArguments $(which exfer || echo ./target/release/exfer) mine --datadir$HOME/.exfer --miner-pubkeyYOUR_PUBKEY_HEX --repair-perms KeepAlive StandardOutPath/tmp/exfer.log StandardErrorPath/tmp/exfer.log EOF launchctl load ~/Library/LaunchAgents/org.exfer.miner.plist ``` ### Technical Analysis The Skill directs the user to create and load a macOS LaunchAgent that executes a cryptocurrency miner. A LaunchAgent survives the original Skill run and starts in later login sessions. The `KeepAlive` property also instructs `launchd` to restart the miner after it exits. Mining is part of the declared Exfer functionality, but cross-session persistence is not required merely to demonstrate or invoke mining. The instructions do not require an explicit persistence confirmation, establish resource limits, or provide corresponding unload and removal commands. The Linux `nohup` example also detaches the miner and keeps it active after the initiating shell exits. Although `nohup` alone does not survive a reboot, it makes resource-consuming execution less visible and harder ...[truncated 1162 chars]- Remediation
View remediation
