Pump and Dump is an AML compliance concept used to identify customers, monitor transactions, and reduce financial-crime risk.
The term “Pump and Dump” refers to an illegal scheme in financial markets where stock prices are artificially inflated through misleading or false information. Once the prices have been driven up, the perpetrators sell off their shares at the inflated price, leaving unsuspecting investors with devalued stocks when the truth emerges.
At its core, a pump and dump operation involves two primary phases:
Pump and dump schemes are illegal and are considered a form of securities fraud. The Securities and Exchange Commission (SEC) in the United States vigorously prosecutes individuals and groups involved in these kinds of activities.
The pump and dump tactic has been around for decades, with notable modern examples often involving penny stocks or cryptocurrencies due to their generally lower regulatory scrutiny and ease of market manipulation:
Understanding pump and dump schemes helps investors avoid falling prey to such manipulations. Common red flags include:
A contrasting scheme, known as “Poop and Scoop,” involves spreading false negative rumors about a stock to drive its price down, allowing fraudsters to buy at a lower price. The process involves:
Keep Pump and Dump tied to the covered entity, activity, rule trigger, filing, disclosure, control evidence, or penalty path. It should not be used as a vague compliance label when the practical question is whether behavior, capital, reporting, investor protection, or enforcement exposure changes.
Use Pump and Dump when a regulated activity depends on who is covered, what conduct is required, what evidence must be kept, and what consequence follows. The finance value of Pump and Dump is identifying the action that changes: filing, disclosure, suitability, capital, controls, investor protection, or enforcement exposure.
A practical review asks three questions: which party has the obligation, which transaction or communication triggers it, and what record proves compliance. If Pump and Dump changes permissible advice, product distribution, reporting, supervision, market conduct, or remediation, Pump and Dump should be reflected in procedures and controls. If Pump and Dump only names a rule, map Pump and Dump to the actual workflow before relying on it.
The practical test for Pump and Dump is whether it changes who is covered, what activity is restricted, what disclosure or filing is required, what evidence must be kept, or what sanction follows. If it does, translate the term into a control step.
Verify Pump and Dump against the rule text, covered-party analysis, transaction record, disclosure, supervisory procedure, retained evidence, and exception log. Pump and Dump matters when filing, conduct, suitability, capital, supervision, remediation, or enforcement exposure changes.
The analysis boundary for Pump and Dump is crossed when covered-party status, required conduct, disclosure, filing, supervision, evidence retention, and enforcement exposure are unchanged. Then it is regulatory background rather than a control action.
Trace Pump and Dump from rule source to covered party, required action, deadline, record, disclosure, supervision, and enforcement risk. Pump and Dump matters when it changes what someone must file, monitor, approve, remediate, retain, or explain to a regulator, customer, board, or counterparty.
The use boundary for Pump and Dump is reached when filing, disclosure, supervision, approval, suitability, capital treatment, remediation, monitoring, and recordkeeping are unchanged. In that case, keep the term as regulatory context rather than a compliance action.
The evidence link for Pump and Dump is the rule citation, filing, disclosure, supervisory record, approval trail, customer record, remediation file, or retention evidence. Without that link, Pump and Dump should not support a compliance conclusion or obligation change.
The risk check for Pump and Dump is whether a compliance conclusion has a covered party, rule source, deadline, evidence, and owner. Test filing, disclosure, suitability, supervision, recordkeeping, remediation, and enforcement exposure before assuming no action is required.
Decision evidence for Pump and Dump should show the rule citation, covered party, required action, deadline, approval trail, filing, disclosure, and retention evidence. Pump and Dump can change compliance analysis only when those facts alter duty, supervision, or enforcement exposure.
Review evidence for Pump and Dump should make the regulatory evidence traceable, not just definitional. For Pump and Dump, tie the evidence to the rule text, regulator guidance, filing, policy memo, and compliance record and explain why that evidence is reliable enough for the finance decision.
Before relying on Pump and Dump, document the decision context: the effective date, reporting period, transition window, and jurisdiction involved. Keep the Pump and Dump evidence trail visible: responsible owner, approval evidence, testing record, remediation status, and disclosure trail. In Regulation work, Pump and Dump matters when it changes permissible activity, capital treatment, reporting duty, customer protection, or enforcement risk.
The practical risk for Pump and Dump is that regulatory terms are unsafe when jurisdiction, effective date, rule source, and compliance evidence are left implicit. If those facts are unavailable, keep Pump and Dump in the explanatory layer instead of treating it as decision-grade evidence.
Use Pump and Dump as a decision workflow, not a static glossary label: define the finance meaning, verify the evidence, and identify which conclusion changes. Start by linking Pump and Dump to rule source, jurisdiction, effective date, covered activity, compliance owner, and enforcement exposure. Only after those checks should Pump and Dump influence a regulatory decision.
For Pump and Dump, confirm the source record, the date or jurisdiction that could change the answer, and the finance decision affected if the evidence were wrong. If those checks are incomplete, keep Pump and Dump as explanatory context rather than a decisive input.