Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
USP — Establishes persistence on a Linux system by creating a udev rule that triggers the execution of a specified payload (binary or script) | Kitploit
Tools/GitHubGitHub/grahamhelton/usp
Privilege EscalationPersistence MechanismsPost-ExploitationRed TeamingPayload Development
GitHubgrahamhelton/usp

USP

Establishes persistence on a Linux system by creating a udev rule that triggers the execution of a specified payload (binary or script)

View Repository
15322342 years agoReviewed by Kitploit
Share

USP

image

Features

This Go program establishes persistence on a Linux system by creating a udev rule that triggers the execution of a specified payload (binary or script). It offers two trigger options:

  • USB Persistence: The payload is executed whenever a USB device is inserted.
  • Boot Persistence: The payload is executed during system boot, leveraging the /dev/random device.

Additionally, it provides a cleanup option to remove the established persistence.

Usage

  1. Compile the Go script: go build -o usp

  2. Run the script with root privileges (sudo): sudo ./usp

You can customize the behavior using the following flags:

  • -f <filename>: Specify the path where the payload will be written (default: /usr/local/bin/persistence).
  • -p <payload>: Specify the path to the payload file (binary or script) that will be executed. This is a required flag.
  • -r <rulesname>: Specify the name of the udev rules file (default: 75-persistence.rules).
  • -usb: Enable USB persistence.
  • -random: Enable boot persistence using /dev/random.
  • -c: Cleanup persistence, removing the payload file and udev rule.

Example

  • The following uses the USB persistence method to run example.sh everytime a USB device is connected.
sudo ./usp -p ./example.sh 
  • The following uses the "random" persistence method to run my_backdoor_binary everytime /dev/random is loaded (such as at boot). It is installed at /bin/ripgrep. (Masquerading as the ripgrep binary). Additionally, the rules file is created in /etc/udev/rules.d/123-notsektchy.rules
sudo ./usp -random  -f /bin/ripgrep -p my_backdoor_binary -r 123-notsketchy.rules

References && Additional Reading

  • https://www.aon.com/en/insights/cyber-labs/unveiling-sedexp
  • https://ch4ik0.github.io/en/posts/leveraging-Linux-udev-for-persistence/
  • https://opensource.com/article/18/11/udev
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    927
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    324
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    289

Explore all tools

Browse our collection of tools

View all tools →