PitchHut logo
The Open-Source, Linux Live Adaptive Identity Engine
Pitch

PH4NTXM is an open-source system framework designed as an adaptive identity engine within a stateless, live-only environment. It constructs coherent system identities at runtime, where observable properties are derived from a unified identity model. Built for security research and adversarial environments, it enables exploration of system behavior, fingerprinting, and correlation resistance.

Description

PH4NTXM

PH4NTXM is a Linux plug-and-play environment that operates as an adaptive identity engine with persona-driven identity synthesis, a runtime enforcement framework, and a controlled execution system within a stateless, live-only environment.

PH4NTXM is not a privacy tool, not a virtual machine, and not a spoofing toolkit. It is a full-system identity synthesis framework.

It constructs fully coherent system identities at runtime, where all observable system properties are derived from a unified identity graph and regenerated per execution.

Each system instance is:

self-contained, non-persistent, non-recoverable, and non-correlatable across sessions.


πŸš€ Getting Started

Getting started is simple:

  1. Install live-build:
sudo apt update
sudo apt install live-build
  1. Clone the repository:
git clone https://github.com/PH4NTXMOFFICIAL/PH4NTXM.git
cd PH4NTXM
  1. Build your ISO:
sudo lb clean
sudo lb config
sudo lb build

That’s it β€” your own ISO, built directly from source.


⚠️ Scope & Intent

PH4NTXM is designed for controlled security research and adversarial system modeling environments where:

  • system compromise is assumed
  • deep inspection is expected
  • identity correlation must be structurally prevented
  • runtime behavior must remain internally consistent under observation

This is not a general-purpose operating system or desktop distribution.


🧠 Core Concept

PH4NTXM does not spoof isolated system attributes.

It generates a complete identity graph, from which all system properties are derived.

Depending on the active persona, identity synthesis follows either:

  • a deterministic, seed-based model (Linux / Windows)
  • or a non-deterministic, entropy-driven model (Lonewolf)

This ensures:

  • cross-layer consistency (hardware, OS, network)
  • controlled identity generation per session
  • bounded variability within persona constraints
  • complete regeneration on every execution

No subsystem operates independently of the identity model.


🧩 Key Features

  • Persona-based execution modes (Linux / Windows / Lonewolf)
  • Full-system identity synthesis at runtime
  • Stateless execution model (RAM-only)
  • Cross-layer identity coherence enforcement
  • Hardware identity virtualization
  • Network behavior derived from the identity graph
  • Active packet-level transformation (TCP/IP mutation layer)
  • Runtime entropy engines (time, memory, and state mutation)
  • Runtime integrity enforcement
  • Multi-stage fail-secure termination with dedicated nuke kernel

🧠 System Model

All observable system outputs are generated from a single runtime identity graph.

This includes:

  • hardware profile
  • CPU / memory / GPU representation
  • network stack behavior
  • DNS and routing characteristics
  • system and application surface properties

The system behaves as a coherent synthetic instance, not a collection of modified components.


πŸ‘€ Personas

PH4NTXM uses boot personas as the root constraint of system identity.

PersonaDescription
LINUXLinux system execution mode
WINDOWSWindows-aligned execution mode
LONEWOLFTor-enforced isolation mode

Each persona defines the bounds of the identity graph and runtime behavior.

LONEWOLF diverges from the deterministic model and operates as a fully entropy-driven, non-correlatable identity mode.


πŸ” Execution Model

  1. Boot environment initialization
  2. Persona selection (boot mode)
  3. Identity seed / entropy initialization
  4. Identity graph construction
  5. Hardware and network synthesis
  6. Runtime enforcement activation
  7. System execution (live-only state)
  8. Continuous integrity monitoring
  9. Controlled termination β†’ transition to nuke kernel

πŸ”’ Runtime Properties

  • Stateless execution (no persistence between sessions)
  • RAM-only system state
  • Continuous identity consistency enforcement
  • Controlled variability within persona-defined bounds
  • Runtime mutation of time, memory, and system surfaces
  • Full system regeneration on reboot

βš™οΈ Network Model

Network behavior is derived from the same identity graph that defines system hardware and runtime state.

This ensures:

  • consistent flow behavior per session
  • persona-aligned TCP/IP characteristics
  • deterministic or entropy-driven packet behavior depending on persona
  • controlled DNS and routing characteristics

PH4NTXM operates an active packet transformation layer, modifying live traffic characteristics while preserving protocol correctness.

In LONEWOLF mode, the network model is replaced by a Tor-enforced, system-wide transparent routing layer, operating under a fail-closed policy.


🧱 Security Model

PH4NTXM enforces:

  • minimal exposure surface
  • hardened kernel configuration
  • restricted introspection and debugging interfaces
  • strict runtime policy enforcement across all layers
  • continuous correction of state deviations

In case of integrity violation or controlled termination:

the system transitions to a fail-secure execution path via a dedicated nuke kernel, resulting in complete session invalidation.


πŸ’£ Fail-Secure Termination

PH4NTXM implements a multi-stage termination architecture:

  • termination hooks bound to shutdown, reboot, and failure paths
  • reserved memory region for secondary kernel execution
  • transition via kexec into an isolated minimal kernel environment
  • forced system halt and memory state invalidation

This guarantees:

  • no recoverable runtime state
  • no residual memory artifacts
  • no post-execution persistence

πŸ“¦ Build Environment

ComponentSpecification
Base OSDebian / XFCE (hardened)
ArchitectureAMD64
ExecutionRAM-only
PersistenceNone

πŸ“œ Design Philosophy

  • Identity is persona-driven, not static
  • Systems must remain coherent under observation
  • No layer exists independently
  • All outputs derive from a single identity source
  • Runtime state must be non-recoverable
  • Every execution is disposable

🀝 Contributing

Contributions are welcome.

You can:

  • audit the system
  • test behavior
  • propose improvements
  • submit patches

πŸ’Έ Support

PH4NTXM is an independent project.

Donations are optional and never required β€” and it’s completely understood that many may not be able to contribute.

If you do choose to support, it is genuinely appreciated and directly helps the project evolve.

Monero (XMR): 43p2cFkaNaaTn2GGgjUab94Qu3TqRWHxbZcmojuqTPZ2WMp8WJS5iKB5AJJtqYRmwRE9Cx3RBHLgiZxByMj2f5HoA6gMS2h


πŸ“„ Licensing

PH4NTXM is licensed under the GNU General Public License v3.0.

See the LICENSE file for details.


πŸ“¬ Contact

All communication should be encrypted.


βš–οΈ Legal

PH4NTXM is intended for lawful security research and controlled environments only.

Users are responsible for compliance with applicable regulations.


Summary

PH4NTXM is an adaptive identity engine with persona-driven identity synthesis, enforcement framework, and integrated runtime mutation with fail-secure termination.

It:

  • generates coherent synthetic identities
  • aligns all system layers through a shared identity graph
  • controls observable system and network surfaces
  • actively transforms network behavior at packet level
  • injects temporal and memory-level variability
  • enforces runtime consistency and integrity
  • provides controlled execution with guaranteed non-recoverability

Each execution is:

a fully consistent, persona-bound, non-reproducible system instance with no survivable state

0 comments

No comments yet.

Sign in to be the first to comment.