PicoStocks Hack

TOTAL LOST $6.4M
Medium Access Control

Summarize with AI

Affected Chain 2013 Incident surface
Recovered $6.4M 100.0% returned
All-Time Rank #385 By amount stolen
Protocol Type Exploit/Access control Target category

Incident Overview

PicoStocks suffered a significant loss due to unauthorized access to their keys, leading to the defunding of both hot and cold wallets

An individual with prior access to PicoStocks' keys exploited this access to drain both the hot and cold wallets of the stock exchange. Despite the substantial loss, PicoStocks managed to cover the entire amount, ensuring that creditors were not affected by this incident

Incident Report

Protocol / Project PicoStocks
Date of Incident
Attack Technique Access Control
Classification CeFi
Primary Source View Post-Mortem

Protocol Information

Protocol Type Exploit/Access control
Official Website picostocks.com/
Protocol Twitter/X @picostocks
Team Anonymous
Source Code Unverified

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 Operational-security tradecraft (phishing, malware, leaked seed phrases, or insider access) to obtain treasury signing authority
Capital Required Minimal capital - only enough to cover gas while draining the compromised accounts
On-Chain Access Valid signing authority over the compromised wallets / multisig signers, allowing direct transfer of funds or stake authorization
Target Reconnaissance Identification of PicoStocks's high-value treasury accounts and the authority / multisig structure controlling them
Execution Speed Speed to drain the compromised accounts before the team detects the breach and revokes signing authority or freezes the assets
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 Access Control audit checklist and test coverage

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

  • Verify all logic paths related to Access Control are guarded by proper access controls and input validation - see the Access Control Attacks attack class for patterns
  • 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

Funds Recovery

100.0%

Recovered

$6.4M

Net Loss

0

Related Attack Classes

The technique used in this hack maps to these vulnerability classes in our security curriculum:

See all Access Control Attacks examples →

Sources & References

Learn to Prevent the Next PicoStocks

The PicoStocks 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.

Recreate exploit patterns safely Free Trial