3ds-rom-crypto

Explain the 3DS ROM encryption/decryption pipeline for NCSD/NCCH.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/londospark/citrust --skill 3ds-rom-crypto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 3ds-rom-crypto
Source: https://github.com/londospark/citrust/tree/main/.squad/skills/3ds-rom-crypto
Command: npx skills add https://github.com/londospark/citrust --skill 3ds-rom-crypto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide provides a comprehensive understanding of the 3DS ROM encryption/decryption pipeline (NCSD/NCCH) and key derivation, enabling researchers and developers to implement or audit decryption workflows in 3DS emulation and tooling.

Core Features & Use Cases

  • Documentation of NCSD/NCCH file layout, including headers, partition tables, and per-partition structures.
  • Step-by-step explanations of key derivation, IV construction, decryption order, and flag patching.
  • Practical use cases for emulator development, forensic analysis, and integrity checks.

Quick Start

Refer to this guide to implement a 3DS ROM decryption workflow in your project.

Frequently Asked Questions about 3ds-rom-crypto

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does 3DS ROM decryption work for NCSD and NCCH partitions?

3DS ROM decryption works by deriving AES-CTR keys, constructing IVs, and applying decryption across NCSD/NCCH partitions. This pipeline involves specific decryption orders and flag patching to correctly process the file layout for analysis.

What is the correct decryption order for NCCH partitions?

The correct decryption order for NCCH partitions requires deriving keys, constructing initialization vectors, and applying patch rules sequentially. Following the documented pipeline ensures proper handling of per-partition structures and accurate firmware analysis.

Do I need specific AES-CTR keys for 3DS ROM firmware analysis?

Yes, 3DS ROM firmware analysis requires specific AES-CTR keys and correct IV construction. Key derivation is necessary to implement or audit the decryption pipeline across NCSD/NCCH partitions for emulator development and security research.

What are the anti-patterns when implementing a 3DS ROM decryption pipeline?

Anti-patterns when implementing a 3DS ROM decryption pipeline involve ignoring proper key derivation, incorrect IV construction, and wrong decryption orders. The guide specifies necessary patch rules to audit workflows and avoid these security research errors.

Can I use this 3DS ROM decryption guide for emulator development?

Yes, you can use this 3DS ROM decryption guide for emulator development. It documents NCSD/NCCH file layouts, headers, and partition tables, providing practical use cases for emulation, forensic analysis, and integrity checks.