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
Silverseal — Linux post-exploitation framework with a UEFI bootkit that persistently and stealthily loads a Rust-based kernel module rootkit on modern Linux systems. | Kitploit
Tools/GitHubGitHub/idov31/silverseal
Persistence MechanismsExploitationPost-ExploitationMalware AnalysisRed TeamingPayload DevelopmentBinary Exploitation
GitHubidov31/silverseal

Silverseal

Linux post-exploitation framework with a UEFI bootkit that persistently and stealthily loads a Rust-based kernel module rootkit on modern Linux systems.

View Repository
1962210410 days agoReviewed by Kitploit
Share

Silverseal - Linux Bootkit Framework

Silverseal Logo

Rust Assembly Linux

Silverseal is an open-source Linux bootkit research framework written in Rust. It demonstrates how a UEFI bootkit hooks the Linux boot process to load a Rust kernel module. The repository contains:

  • silverseal-bootkit/: the no_std UEFI bootkit, with architecture-specific assembly under asm/.
  • silverseal-rootkit/: the Kbuild-managed Rust Linux kernel module.
  • scripts/: environment, deployment, and recovery helpers.

The project explores UEFI bootkit development, Linux boot-chain hooking, kernel-module loading, and pre-OS persistence in a research environment.

Design

Silverseal Design Diagram

x64 boot flow

  1. grubx64.efi is replaced by silverseal-bootkit.efi; the original is retained as grubx64.efi.original.
  2. The bootkit loads the saved GRUB image, hooks its Linux boot-image function, and starts GRUB. When GRUB takes its existing Linux boot path, the hook restores the original function and detours the kernel image's zstd decompressor.
  3. After the decompressor returns, the bootkit locates a late-initcall entry in the decompressed kernel. It places a stager and worker in .text code caves, keeps their work_struct and arguments in a .data cave, and redirects that initcall entry to the stager.
  4. During kernel initialization, the stager queues the worker with schedule_work, then jumps to the original initcall so it still runs.
  5. The worker sleeps for 10 seconds, then calls call_usermodehelper to run /sbin/insmod /silverseal_rootkit.ko from the real root filesystem.

The x64 kernel hook uses signatures and layout assumptions from a specific Ubuntu kernel image. Matching build artifacts alone does not establish that the hook will work on another kernel; validate the target image and boot behavior in a disposable VM.

ARM64 boot flow

ARM64 mirrors the existing x86 deployment model:

  1. grubaa64.efi is replaced by silverseal-bootkit.efi; the original is retained as grubaa64.efi.original.
  2. The bootkit chain-loads that original GRUB image and detours its existing Linux boot-image path. It does not add or require a GRUB menu entry.
  3. The bootkit finds the stock ARM64 zboot PE inside the staged vmlinuz .linux section and observes its successful decompression into vmlinux.
  4. The decompressed kernel is matched against the exact target profile. A late-initcall entry is redirected to a position-independent stager.
  5. The stager initializes a kernel work_struct and calls the target kernel's schedule_work.isra.0. Its worker sleeps for 10 seconds, then invokes /sbin/insmod /silverseal_rootkit.ko from the real root filesystem.
  6. The original initcall still runs.

Prepare a build environment

On Ubuntu, install_dependencies.sh installs build packages, Rust and rust-src, and bindgen-cli. It also checks whether the running kernel advertises CONFIG_RUST=y. Review the script before running it because it installs packages and changes the default Rust toolchain:

./scripts/install_dependencies.sh

On WSL2 with Ubuntu, wsl_setup.sh prepares a custom Rust-enabled WSL2 kernel, a modules VHDX, and a build tree for external modules. It can optionally write a Windows .wslconfig entry. Review its options and the changes it makes before running it:

./scripts/wsl_setup.sh --help
./scripts/wsl_setup.sh

The pinned ARM64 Ubuntu target has a separate setup flow below. ubuntu_target_setup.sh runs natively in that ARM64 VM and derives the required Rust version from its kernel configuration; it is not a generic WSL cross-build helper.

Build the ARM64 rootkit in the Ubuntu VM

Use the native ARM64 Ubuntu VM on Apple Silicon. The real module must be built through the target kernel's Kbuild tree, not with Cargo's IDE stub:

cd Silverseal
./scripts/ubuntu_target_setup.sh 7.0.0-31-generic

cd silverseal-rootkit
make clean ARCH=arm64 LLVM= KDIR=/lib/modules/7.0.0-31-generic/build
PATH=/usr/bin:/bin:$PATH \
RUST_LIB_SRC=/path/printed/by/ubuntu_target_setup.sh \
make RUST_MIN_TOOLCHAIN= \
  ARCH=arm64 \
  LLVM= \
  KDIR=/lib/modules/7.0.0-31-generic/build \
  RUSTC=rustc-1.93 \
  RUSTDOC=rustdoc-1.93

Confirm that Kbuild produced the module for the pinned kernel:

file target/arm64/7.0.0-31-generic/silverseal_rootkit.ko
modinfo target/arm64/7.0.0-31-generic/silverseal_rootkit.ko | grep vermagic

Before runtime testing, validate the target kernel's work_struct layout from its BTF or DWARF: size 32 bytes, entry at offset 8, and func at offset 24. A mismatch is a hard stop because those values are encoded by the stager.

Build the ARM64 bootkit on macOS

Apple Silicon can build the AArch64 UEFI binary directly. Install stable Rust with the aarch64-unknown-uefi target and PowerShell (pwsh) for fixture verification.

The large pinned artifacts are expected in tmp/silverseal-kernel-7.0.0-31-generic/. Generate the v3 profile after verifying their hashes, unique signatures, nested stock-zboot PE, caves, initcall, and linked System.map evidence:

cd Silverseal
pwsh ./scripts/verify_arm64_fixture.ps1 \
  -ArtifactDirectory ./tmp/silverseal-kernel-7.0.0-31-generic \
  -OutputDirectory ./target/arm64-fixture/7.0.0-31-generic-v3

export SILVERSEAL_ARM64_PROFILE="$PWD/target/arm64-fixture/7.0.0-31-generic-v3/7.0.0-31-generic.ssarm64p"
cargo build-bootkit-arm64 --release

The result is:

target/aarch64-unknown-uefi/release/silverseal-bootkit.efi

An ARM64 build with no SILVERSEAL_ARM64_PROFILE deliberately installs no hook. The profile and small signature fixtures live under fixtures/arm64/7.0.0-31-generic/; the large kernel and GRUB artifacts remain ignored.

Host-side contracts can be run with:

cargo test-arm64
cargo test -p silverseal-bootkit --bin silverseal-arm64-tool --features arm64-tools

Deploy in the ARM64 Ubuntu VM

Copy the bootkit and module into the VM, then put the module on the real root filesystem and replace the existing ARM64 GRUB binary:

sudo install -m 0644 \
  silverseal-rootkit/target/arm64/7.0.0-31-generic/silverseal_rootkit.ko \
  /silverseal_rootkit.ko

sudo ./scripts/setup_silverseal.sh arm64 \
  target/aarch64-unknown-uefi/release/silverseal-bootkit.efi
sudo reboot

Do not create a menu entry and do not rebuild initramfs. The VM should boot its normal existing Ubuntu entry. After boot, inspect the module result with:

sudo dmesg -w
lsmod | grep silverseal_rootkit

To restore the saved original GRUB image:

sudo ./scripts/restore_silverseal.sh arm64

The restore helper keeps the replaced image as grubaa64.efi.silverseal for recovery.

Serial logs with VMware Fusion on macOS

Add a virtual serial port to the powered-off ARM64 VM and configure its output to a file on macOS. The bootkit discovers the firmware's UEFI Serial I/O protocol; it does not assume QEMU's PL011 MMIO address. If Fusion firmware exposes no Serial I/O protocol, logging is silently disabled and boot continues.

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.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    510
  • 3

    ARTEX

    baarai/artex

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

    415
  • 4

    redforge

    cybersecurity91/redforge

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

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 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.

    258

Explore all tools

Browse our collection of tools

View all tools →