How much was lost in the PRXVT hack?

The PRXVT hack resulted in $97K in losses on January 01, 2026.

What attack technique was used in the PRXVT exploit?

The PRXVT exploit utilized Sybil Attack with CREATE2 Addresses. Understanding this attack vector is critical for smart contract auditors and developers building secure DeFi protocols.

How can developers prevent similar smart contract attacks?

Preventing smart contract hacks requires a combination of secure coding practices, thorough security audits, and understanding common attack vectors like reentrancy, oracle manipulation, and access control flaws. Smart Contract Hacking (SCH) provides hands-on training to help developers and auditors identify and prevent vulnerabilities before deployment.

PRXVT Hack

TOTAL LOST $97K

Low Jan 01, 2026 Sybil Attack with CREATE2 Addresses base

Affected Chain base Incident surface

Recovered - No recovery reported

All-Time Rank #1538 By amount stolen

Year 2026 Incident year

Incident Report

Protocol / Project PRXVT

Date of Incident January 01, 2026

Affected Chain(s) base

Attack Technique Sybil Attack with CREATE2 Addresses

Classification Protocol Logic

Primary Source View Post-Mortem

What the Attacker Needed to Succeed

Understanding the prerequisites for this type of attack helps auditors identify protocols that are most at risk and helps developers build better defenses.

Technical Knowledge Deep understanding of sybil attack with create2 addresses and Solidity and EVM internals

Capital Required Seed capital to cover gas and initial position setup

On-Chain Access Ability to interact with base smart contracts and deploy a custom exploit contract

Protocol Analysis Identification of the exploitable vulnerability in PRXVT's contract logic - root cause: protocol logic

Execution Speed Precise transaction ordering and timing to exploit the vulnerability within a single atomic block

Obfuscation Plan A strategy to launder and move stolen funds - typically through mixers, cross-chain bridges, or decentralized DEX swaps to resist tracing

What Auditors Should Check

Could this have been caught in audit? Likely — with a thorough Sybil Attack with CREATE2 Addresses audit checklist and test coverage

If you're auditing a protocol with similar architecture to PRXVT, these are the critical security checks that could have prevented this incident (January 2026).

Verify all logic paths related to Sybil Attack with CREATE2 Addresses are guarded by proper access controls and input validation
Review privileged functions (owner, admin, governance) for potential abuse vectors - centralization risks should be documented and bounded with timelocks or multi-sigs

Master these auditing techniques with hands-on labs and real exploit scenarios in the Smart Contract Hacking course.

Free Trial

Proof-of-Concept Exploits

1 PoC available

poc-exploits - prxvt

$ PRXVT Bussiness Logic Flaw

On-Chain Evidence & References

Twitter/X Alert https://x.com/CertiKAlert/status/2006685174587605315

Sources & References

01
Source 1 https://x.com/CertiKAlert/status/2006653156927889666

Threat Assessment

Severity Level

LOW

Attack Vector Sybil Attack with CREATE2 Addresses
Root Cause Protocol Logic
Year 2026

Learn to Prevent the Next PRXVT

The PRXVT hack is one of many attacks that skilled auditors are trained to detect before deployment. Master real exploit patterns and defense techniques with hands-on Web3 security training.

Start Free Trial Browse Attack Library