Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
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.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
xz-vulnerable-honeypot — An ssh honeypot with the XZ backdoor. CVE-2024-3094 | Kitploit
Tools/GitHubGitHub/lockness-ko/xz-vulnerable-honeypot
Defensive ToolsVulnerability AnalysisNetwork SecurityThreat IntelligenceIncident Response
GitHublockness-ko/xz-vulnerable-honeypot

xz-vulnerable-honeypot

An ssh honeypot with the XZ backdoor. CVE-2024-3094

View Repository
1471912 years agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

xz-vulnerable-honeypot

An ssh honeypot with the XZ backdoor. CVE-2024-3094

TODO: hook the backdoor and/or sshd. log rsa keys for decryption.

notes:

  • https://gist.github.com/smx-smx/a6112d54777845d389bd7126d6e9f504
  • https://gist.github.com/q3k/af3d93b6a1f399de28fe194add452d01
  • https://github.com/hamarituc/xz-backdoor

Warning

PLEASE run this on a separate isolated system. Docker is configured in a way that allows a threat actor to easily escape it. Docker is only used to get all the shared libraries working and configured.

Installation

Install notify by projectdiscovery using the following command:

root@kitploit:~
go install -v github.com/projectdiscovery/notify/cmd/notify@latest

Run the following command to start the honeypot:

root@kitploit:~
./monitor.sh DISCORD_WEBHOOK_URL

e.g.

root@kitploit:~
./monitor.sh https://discord.com/api/webhooks/12345678909876/aaaaaaaa

This will use notify to send all logs to a discord webhook.

How it works

The vulnerable version of xz (5.6.1) and the liblzma linked version of sshd from the fedora repositories are ran in the configuration that activates the backdoor. Monitoring is provided by bpftrace, strace, tcpdump, and the sshd process itself.

  • bpftrace
    • Syscall monitoring and shared library hooking.
  • strace
    • Syscall montioring for the parent sshd process.
  • tcpdump
    • Capturing packets.
  • sshd
    • Login events (NOTE This will most likely not capture the login event for a bad actor as the backdoor uses set_log_mask to change the logging behaviour when the attacker attempts to login)
Download Tool