Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
mukul975 avatar

Analyzing Persistence Mechanisms In Linux

  • 254 installs
  • 27.3k repo stars
  • Updated August 2, 2026
  • mukul975/anthropic-cybersecurity-skills

Analyzing Persistence Mechanisms In Linux is an agent skill that guides systematic review of Linux persistence tradecraft for solo operators.

About

Analyzing persistence mechanisms in Linux is an agent skill for solo and indie builders who run Linux APIs, CLIs, or self-hosted agents and need disciplined ways to find how attackers survive reboots. The skill name targets cron jobs, systemd units, startup scripts, authorized keys, and similar footholds that are easy to miss when you ship fast without a dedicated SOC. Use it during ship security reviews, after a suspected breach, or when operate-phase logs show recurring unknown processes. It lives in a cybersecurity skills collection so your coding agent can walk checklists instead of improvising grep one-liners. Expect procedural guidance rather than a live scanner MCP; you still run commands on the host. Best for builders who own their VPS, homelab, or small fleet and want repeatable persistence triage without hiring a full-time analyst.

  • Structures Linux persistence analysis for incident response and threat-hunting workflows
  • Aligns with cybersecurity skill packs aimed at solo operators auditing servers and agents
  • Apache 2.0 licensed material suitable for reuse in agent skill libraries
  • Complements ship-phase hardening before expose-to-internet launches
  • Pairs with broader anthropic-cybersecurity-skills for defense-in-depth reviews

Analyzing Persistence Mechanisms In Linux by the numbers

  • 254 all-time installs (skills.sh)
  • +16 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #680 of 2,203 Security skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill analyzing-persistence-mechanisms-in-linux

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs254
repo stars27.3k
Security audit3 / 3 scanners passed
Last updatedAugust 2, 2026
Repositorymukul975/anthropic-cybersecurity-skills

What it does

Guide an agent through systematic detection and analysis of Linux persistence techniques after compromise or during hardening reviews.

Who is it for?

Best when you're self-hosting on Linux and need a repeatable persistence checklist during security reviews or incident triage.

Skip if: Skip if you only build on managed PaaS with no SSH access, or cases where you already have a completed EDR report and only need ticket closure.

When should I use this skill?

You need to analyze or document Linux persistence mechanisms during a security review, incident, or post-deploy audit.

What you get

You get a structured persistence review plan your agent can execute so residual access paths are documented and prioritized for removal.

  • Prioritized list of suspicious persistence locations
  • Notes tying each finding to evidence commands and remediation steps

Files

SKILL.mdMarkdownGitHub ↗

Analyzing Persistence Mechanisms in Linux

Overview

Adversaries establish persistence on Linux systems through crontab jobs, systemd service/timer units, LD_PRELOAD library injection, shell profile modifications (.bashrc, .profile), SSH authorized_keys backdoors, and init script manipulation. This skill scans for all known persistence vectors, checks file timestamps and integrity, and correlates findings with auditd logs to build a timeline of persistence installation.

When to Use

  • When investigating security incidents that require analyzing persistence mechanisms in linux
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Root or sudo access on target Linux system (or forensic image)
  • auditd configured with file watch rules on persistence paths
  • Python 3.8+ with standard library (os, subprocess, json)
  • Optional: OSSEC/Wazuh agent for file integrity monitoring alerts

Steps

1. Scan Crontab Entries — Enumerate all user crontabs, /etc/cron.d/, /etc/cron.daily/, and anacron jobs for suspicious commands 2. Audit Systemd Units — Check /etc/systemd/system/ and ~/.config/systemd/user/ for non-package-managed service and timer units 3. Detect LD_PRELOAD Hijacking — Check /etc/ld.so.preload and LD_PRELOAD environment variable for injected shared libraries 4. Inspect Shell Profiles — Scan .bashrc, .bash_profile, .profile, /etc/profile.d/ for injected commands or reverse shells 5. Check SSH Authorized Keys — Audit all authorized_keys files for unauthorized public keys with command restrictions 6. Correlate Auditd Logs — Search auditd logs for file modification events on persistence paths to build an installation timeline 7. Generate Persistence Report — Produce a risk-scored report of all discovered persistence mechanisms

Expected Output

  • JSON report of all persistence mechanisms found with risk scores
  • Timeline of persistence installation from auditd correlation
  • MITRE ATT&CK technique mapping (T1053, T1543, T1574, T1546)
  • Remediation commands for each detected persistence mechanism

Related skills

How it compares

Use as a procedural hunt playbook instead of ad-hoc shell greps or assuming a generic linter catches backdoors.

FAQ

Who is analyzing persistence mechanisms in linux for?

Developers and small teams who operate Linux servers, CLIs, or agents and need agent-guided persistence analysis without a full security operations team.

When should I use analyzing persistence mechanisms in linux?

During ship security hardening before launch, after suspicious operate-phase alerts, or when validating a recovered VPS before putting it back in production.

Is analyzing persistence mechanisms in linux safe to install?

Review the Security Audits panel on this Prism page and the upstream repo license; the bundled readme here is license text only, so verify SKILL.md and scripts before granting shell on production hosts.

Securityappsecaudit

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.