IonCube Decoder for PHP 8.2
Online

PHP 8.2 at a glance

Released

December 2022

End of life

December 2025

Zend engine

Zend Engine 4.2

IonCube encoders that target it

IonCube 14 was the first release with PHP 8.2 parity. IonCube 15 also targets 8.2.

What PHP 8.2 introduced

Decoders for PHP 8.2 need to reconstruct opcodes for these language features specifically:

• Readonly classes (class X { public readonly int $id; })
• Disjoint normal form (DNF) types (A&B | null)
• true, false, and null as standalone types
• New random number API (\\Random\\Randomizer)
• Dynamic property deprecation (#[AllowDynamicProperties] attribute)
• Constants in traits
• Sensitive parameter attribute

Why PHP 8.2 decoding still matters

• PHP 8.2 is the most common 'current' deployment target in 2025–2026 for new commercial scripts.
• Hosting providers that upgraded past PHP 7.x commonly settled on 8.2 before jumping to 8.3/8.4.
• WHMCS 8.x strong-recommended PHP 8.2 for modern installs, so the ecosystem adoption is high.

Gotchas specific to decoding PHP 8.2

• DNF type opcodes (TYPE_INTERSECTION inside TYPE_UNION) are new in 8.2; mistyping by decoder produces syntactically invalid PHP.
• Dynamic property deprecation means decoded classes may need explicit property declarations or the #[AllowDynamicProperties] attribute to run.
• Random\Randomizer opcodes call into the new randomizer — 8.1 decoders handle it as a generic method_call, losing type information.

File signature

An IonCube-encoded file targeting PHP 8.2 typically begins with a header that looks like this:

<?php //004fb5a6\n<?php //PHP82+\nHR+cPkX...

The first line encodes a header hash, the second encodes the PHP target, and the remainder is the encrypted bytecode payload. Our free in-browser version detector reads these bytes to identify the exact encoder and PHP target for your file.