Risks in Crypto
Nobody broke in. The permissions were theirs all along.
A hack comes from outside. A rug pull comes from inside the project itself: the people responsible build up trust, then leave with the capital. Not a technical accident — a deliberate deception, and one whose warning signs can be checked.
The problem
Nobody broke in.
The last lesson looked at capital being taken by an outsider who found a weakness. Run the same investigation here and it comes back empty. Then ask the other question.
Yesterday it traded. Today it cannot be sold.
CAUSE · UNKNOWNThe pool that stood behind the token is empty and holders cannot get out. Start where an investigation into a loss normally starts: look for the break-in.
Who held which permission
Nothing has been checked yet. Press Check for a breach.
A hack has to get in. It needs a weakness, and the weakness is the whole story — which is why the previous lesson could point at the part that broke. Here there is no part that broke. Every transaction was authorised, every rule in the contract was followed, and the loss is total anyway. Nothing failed, so nothing can be patched.
Broken into, versus never needing to break in. That is the entire difference between the last lesson and this one. A hack is an outsider defeating a control. A rug pull is an insider using one. Users believed they were putting money into a real project, while the people responsible were free to leave the market whenever they chose — and the permission that allowed it was a published property of the contract, not a secret. That is why this is classed as fraud rather than as a fault: it is a trust and incentive problem, not a technical accident.
An illustrative reconstruction of the pattern the source describes. It is not a record of any real event, and no project, token, person or platform is named anywhere in this lesson.
The definition
Three things that follow from an empty breach report.
Tap each card for what it actually means.
Hands on
Seven observations. Only four are warning signals.
Two of the seven are genuinely reassuring, and one carries no information in either direction. Pick an observation, read it, then call it. Marking everything as a warning signal scores badly here — deliberately.
Choose an observation above, then call it.
Call every observation a warning signal and you finish this beat at 4 of 7. That is its own failure mode: a reflex that treats every project as fraud cannot tell a locked pool from an unlocked one, or a published audit from none, so it never produces anything you can actually act on — and it leaves you exactly as exposed as before. No single signal proves fraud. Several together raise the risk sharply. And a project showing none of them has not been cleared of anything: these checks reveal risk, they never certify its absence.
The bridge
Three forms, and the question underneath all of them.
Different routes, one shape: capital leaves through a door the project already held the key to.
Notice what the closing question is not about. It does not ask how fast the price is rising or how viral the story has become — a rising chart and a loud community are compatible with every one of the three forms above. It asks who holds the liquidity, the supply and the contract permissions, and what that party could do with them. Asking it does not make anything safe; it only tells you where the power sits. That is the last of the risks in this section that comes from inside crypto. The final lesson turns to one that comes from outside it entirely: regulation.
Check yourself
Five questions.
Answers come straight from this lesson. Submitting completes it.