T06 · System Persistence
- Location
dlt_restore.py:61- Finding
Recurring Windows Scheduled Task Runs with SYSTEM Privileges
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a disclosed lottery-analysis tool, but it asks for and implements SYSTEM-level scheduling plus cross-user WorkBuddy access and file mirroring that are excessive for that purpose.
Install only if you are comfortable reviewing and disabling the Windows SYSTEM scheduler, cross-user WorkBuddy checks, and peer mirroring behavior. For normal use, prefer running python run_dlt.py manually as the current user, avoid administrator restore operations from untrusted backups, and do not rely on the ledger encryption for strong protection.
dlt_restore.py:61Recurring Windows Scheduled Task Runs with SYSTEM Privileges
dlt_restore.py:46Untrusted Backup XML Can Replace a Privileged Scheduled Task
dlt_healthcheck_all.py:122Health Check Enumerates User Profiles and Reads WorkBuddy Agent Databases
dlt_smart.py:364Default Workflow Writes Reports into Other Users' Agent Skill Installations
dlt_ledger.py:48Custom Ledger Encryption Does Not Authenticate Ciphertext
dlt_outlet_map.py:33TLS Certificate and Hostname Verification Disabled for IP Geolocation
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Enforcing presence of 'prediction', 'expert recommendation', and 'machine learning prediction' report sections conflicts directly with the manifest's anti-prediction/no-edge positioning. This suggests the safety messaging is secondary to a prediction-oriented product, which is dangerous because it can misrepresent the true purpose to reviewers and users.
Detected: suspicious.insecure_tls_verification