T06 · System Persistence
- Location
operations.md:106- Finding
Highest-Privilege SYSTEM Scheduled Task Persistence
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a lottery analysis/reporting tool, but it asks for privileged scheduled execution and can read or write across local user profiles, so it needs careful review before installation.
Use this only under a normal user account and avoid creating the SYSTEM/highest scheduled task. Treat the WorkBuddy integration, peer-install mirroring, and optional local server as high-impact features that should be disabled or reviewed first; offline/manual use of python run_ssq.py is much safer.
operations.md:106Highest-Privilege SYSTEM Scheduled Task Persistence
ssq_healthcheck_all.py:133Cross-User WorkBuddy Database Enumeration and Access
ssq_smart.py:340Cross-User Modification of Peer Skill Installations
ssq_serve.py:91Directory Traversal in the Optional Local Report Server
The documented ability to modify Windows scheduled-task settings is unrelated to the user-facing purpose of lottery randomness education and materially expands the skill's control over the host environment. Any agent that can alter scheduler behavior can weaken safeguards, persistence settings, runtime context, or execution conditions, which creates a real host-level integrity and persistence risk if invoked outside strict boundaries.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
Searching local files for reports and validating expected HTML sections is mostly internal QA behavior, not a direct security flaw. It is still a scope mismatch and contributes to overbroad package behavior, but the standalone risk is limited compared with the network/server/scheduler issues.
No suspicious patterns detected.