Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/rsactftoolCryptography and Web3

rsactftool

⁨Auth/lab ref: RSA testing automation tool for weak public keys. For targeting RSA key recovery or plaintext recovery from public data (n, e, ciphertext, partial leaks).⁩

v2026.11.13-21cd5682 installs+2 in 7 days39 StarsMITsynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/rsactftool

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
qg3qd/PjEU…yADTDLCA==The CLI checks the SHA-256 and the signature before it writes a file.
Packageea2f0bcb…c6a20b3a
ea2f0bcbaff9…2cabc6a20b3a4 files · ⁦4.2 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/cryptography/rsactftool@21cd568

Multi-attack RSA solver for weak RSA scenarios. Best used as a triage engine: feed known key material, run constrained attacks first, escalate only when signal supports it.

Core workflow

  1. Normalize input (.pem, OpenSSH pubkey, or raw n/e).
  2. Inspect key parameters and weakness indicators.
  3. Select attack families by signal (not brute-force all blindly).
  4. Recover private key and/or decrypt ciphertext.
  5. Verify output format and cryptographic consistency.

Quick commands

bash
# Recover private key (auto attack selection)
RsaCtfTool --publickey key.pub --private

# Force a specific attack
RsaCtfTool --publickey key.pub --attack wiener --private

# Decrypt a ciphertext file once key is recoverable
RsaCtfTool --publickey key.pub --decryptfile ciphertext.bin

# Build pubkey from n/e (for problem specifications that give integers only)
RsaCtfTool --createpub -n <n> -e <e>

# Dump key parameters for triage
RsaCtfTool --dumpkey --ext --key key.pub

Attack selection heuristics

  • Start with non-factorization attacks when evidence indicates weak d, broadcast, shared n, or partial leakage.
  • Prioritize factorization when n structure suggests close primes, smoothness, reused factors, or vulnerable keygen.
  • Use scenario-specific methods when custom prime construction or non-standard modulus generation is suspected.

Practical attack loop

bash
# 1) Parse and inspect
RsaCtfTool --dumpkey --ext --key key.pub

# 2) Run fast specific checks first
RsaCtfTool --publickey key.pub --attack wiener --private
RsaCtfTool --publickey key.pub --attack hastads --private
RsaCtfTool --publickey key.pub --attack common_factors --private

# 3) Escalate to broader runs
RsaCtfTool --publickey key.pub --private

# 4) If key recovered, decrypt material
RsaCtfTool --publickey key.pub --decryptfile ct.bin

Output validation checklist

  • Decrypted bytes decode cleanly (UTF-8/ASCII) or have expected binary structure.
  • PKCS#1 padding assumptions are consistent with implementation.
  • If multiple candidate plaintexts appear, test all against oracle verification or remote service.
  • Never trust a single lucky decode without re-encryption consistency checks.

Boundaries

  • Tool scope is RSA semiprime attacks on weak public keys (standard asymmetric key scenarios).
  • Hash cracking (MD5/SHA/bcrypt) is intentionally out of scope here (covered by hashcat skills).

Resources

  • references/factorization-attacks.md — RSA attacks based on factoring n (Fermat, Pollard variants, ECM, QS, etc.).
  • references/non-factorization-attacks.md — RSA attacks without directly factoring n (Wiener, Hastad, Boneh-Durfee, partial leaks, lattice).
  • references/challenge-specific-attacks.md — scenario-specific attacks for non-standard RSA key patterns and triage patterns.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568ea2f0bcbSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login