T06 · System Persistence
- Location
scripts/install.sh:72- Finding
Installer Registers Persistent Scheduled Tasks Without Prior Opt-In
- Content
View full analysis
/dev/null | grep -v "subconscious_metabolism.py tick"; \ echo "*/5 * * * * $_tick_cmd >> $LOGS_DIR/subconscious_tick.log 2>&1" \ ) | crontab - # Rotate every hour (with promotion) ( crontab -l 2>/dev/null | grep -v "subconscious_metabolism.py rotate"; \ echo "0 * * * * $_rotate_cmd >> $LOGS_DIR/subconscious_rotate.log 2>&1" \ ) | crontab - # Daily review at 6am ( crontab -l 2>/dev/null | grep -v "subconscious_metabolism.py review"; \ echo "0 6 * * * $_review_cmd >> $LOGS_DIR/subconscious_review.log 2>&1" \ ) | crontab - # Weekly benchmark Monday 9am ( crontab -l 2>/dev/null | grep -v "subconscious_benchmark"; \ echo "0 9 * * 1 $_bench_cmd >> $LOGS_DIR/subconscious_benchmark.log 2>&1" \ ) | crontab - echo " Cron jobs installed." ``` ### Technical Analysis Running the general-purpose installer automatically modifies the current user's crontab and registers four persistent jobs. The installer does not ask for confirmation or require an explicit option such as `--enable-cron`. The registered tasks execute every five minutes, hourly, daily, and weekly. Most notably, the hourly task enables automatic pending-to-live promotion through `--enable-promotion`. Although scheduled metabolism is related to the declared continuous-learning functionality, it is not the least-privileged installation mode: all operations can be run manually, an ...[truncated 1347 chars]- Remediation
View remediation
