🕑 Estimated reading time: 4 minutes  |  Last updated: May 12, 2026

An insider threat is a risk posed by people with legitimate access, such as employees and contractors, who misuse it deliberately or accidentally. In May 2025, Coinbase disclosed that criminals had bribed a small number of overseas support agents to copy customer data, then demanded $20 million, which Coinbase refused to pay. Defences include least-privilege access, data masking, monitoring for unusual lookups and exports, strong vendor oversight, background checks, a speak-up culture and fast offboarding.

People working late in a modern office at night

Security teams spend most of their energy keeping attackers out. But some of the most damaging incidents come from people already inside: an employee who sells data, a contractor who is bribed, or a well-meaning worker who sends a spreadsheet to the wrong address. These are insider threats, and they are notoriously hard to spot because the activity often looks like normal work.

The Coinbase Case

On 11 May 2025, Coinbase received an extortion email. Criminals claimed to hold customer data and demanded $20 million. Coinbase’s investigation found that the attackers had bribed a small number of overseas customer-support contractors and employees to copy information from internal support tools. The data included names, addresses, phone numbers, emails, partial Social Security numbers, masked bank details and ID images. Passwords, private keys and funds were not accessed.

Coinbase refused to pay, fired the people involved, notified regulators and affected customers, offered a $20 million reward for information leading to the criminals’ arrest and said it would reimburse customers tricked into sending funds. A state regulatory filing later put the number of affected users at nearly 70,000. The stolen data was valuable because it enabled convincing impersonation scams: a fraudster who knows your address and recent balance sounds very much like real customer support.

Types of Insider Threats

Warning Signs

Technical Controls That Help

  1. Least privilege: give each role only the data and functions it needs.
  2. Data masking: show partial information by default, revealing full details only with justification.
  3. Context-based access: require an open support case before a customer record can be opened.
  4. Rate limits: cap how many records an agent can view per hour.
  5. User behaviour analytics: alert on unusual patterns compared with peers.
  6. Data loss prevention: block or flag uploads, downloads and copy-paste of sensitive data.
  7. Secure work environments: virtual desktops that prevent local storage, screen capture and personal devices in support centres.
  8. Logging and auditing: keep tamper-resistant logs and review them.

Human and Organisational Controls

If You Suspect an Insider

Move carefully. Preserve evidence, involve HR and legal early, limit the person’s access discreetly where needed, and avoid tipping them off before you understand the scope. If personal data has been exposed, data protection breach notification rules may apply, including the 72-hour regulator deadline under the GDPR and Nigeria’s Data Protection Act.

Protecting Customers After a Leak

Insider leaks are often followed by scams. Warn customers clearly about what data was exposed and that you will never ask for passwords, seed phrases or transfers to “safe” wallets. Coinbase’s customer warnings and reimbursement pledge are examples of steps that reduce harm.

Limit what a single employee can access

Insider threats cannot be eliminated, but they can be contained. The aim is to make sure that no single person can quietly walk away with vast amounts of sensitive data, and that if someone tries, you notice quickly. That requires both technology and a workplace culture where people feel able to say “someone offered me money for customer data.”

Frequently Asked Questions

Are insider threats common?

Yes. Surveys consistently show that many incidents involve insiders, whether malicious or accidental.

Is monitoring employees legal?

Generally yes if it is proportionate, transparent and has a lawful basis under data protection law.

Did Coinbase pay the ransom?

No. It refused and offered a $20 million reward for information on the attackers instead.

Leave a Reply

Your email address will not be published. Required fields are marked *