<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Keylogger on Vanilla InfoSec</title>
    <link>/tags/keylogger/</link>
    <description>Recent content in Keylogger on Vanilla InfoSec</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/keylogger/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Rust Malware Development - Linux Keylogger</title>
      <link>/posts/rust-malware-development---linux-keylogger/</link>
      <pubDate>Thu, 04 Sep 2025 00:00:00 +0000</pubDate>
      <guid>/posts/rust-malware-development---linux-keylogger/</guid>
      <description>Overview Keyloggers remain a valid TTP for offering deep insight into user behavior. I wanted to write one in Rust aiming for a binary that was memory-safe and efficient (I&amp;rsquo;m really just learning Rust because it&amp;rsquo;s trendy and my coworkers like using it).&#xA;We will be leveraging the evdev interface — the Linux kernel’s raw input event device system. This gives us direct, low-noise access to keystroke events from /dev/input/event*</description>
    </item>
  </channel>
</rss>
