Employees From Hell: What Disgruntled Insiders Actually Do, and How to Survive It

You have heard the compliance boilerplate. Insider threats are your most dangerous risk vector. What you have not heard is what that looks like when it lands on your desk at 7 a.m. on a Tuesday.

This is not a theoretical exercise. The tactics below are written from the adversary point of view. They map onto gaps that exist in almost every small RIA, broker-dealer, and fund operation we have assessed.

The goal is not to scare you. It is to make you specific. Vague awareness of insider threats does not drive policy changes. Knowing what a furious former compliance officer, a terminated portfolio manager, or a bitter operations manager can actually do is what moves the needle.

The frame before the war stories

CISA splits insider threats into two kinds. Unintentional and intentional. Unintentional covers the negligent and the accidental, the lost laptop and the misdirected email. Intentional covers what this brief is about. Sabotage, theft, espionage, and the cyber expressions of all three.

CISA also gives you the lifecycle to run against the problem. Define the threats specific to your firm. Detect and identify them. Assess the risk. Manage it before behavior turns into an incident. Every defense in this brief sits somewhere on that lifecycle.

One number worth holding onto. Cost data cited in CISA’s insider threat guidance shows the financial impact of insider incidents falls hardest on organizations with fewer than 500 employees. That is your client. In most cases, that is you.

Who we are talking about

The insider threat at a financial firm is not usually a spy. It is someone you promoted once. You trusted them with client relationships. Then you let them go when the fund underperformed, when the culture soured, or when an exam went sideways and someone had to carry it.

They know your clients by name. They know your AUM. They know which accounts are problems and which principals have history. They know your custodian relationships, your ADV disclosures, and which corners you cut in your compliance policies and procedures.

That knowledge is the weapon. Everything below is a delivery mechanism.

Case 01 — The Regulatory Grenade

What they do. They file a detailed, credible complaint with the SEC, FINRA, or your state securities regulator. Sometimes all three at once.

The amateur files a vague complaint. The insider files a specific one. They cite real account numbers, real dates, and real compliance gaps. They do not have to invent much, because they lived inside the operation. A complaint that is 80 percent distortion still lands hard when 20 percent of it checks out.

They may also file an IRS Form 3949-A alleging tax irregularities, or a tip to FinCEN. These get routed, logged, and resurface during an examination, sometimes years later.

Why it hurts. A regulatory complaint from a credible former employee is not something you rebut with a letter. A complaint that specific typically triggers an inquiry. At worst it triggers a full examination, timed to your worst possible moment. Mid raise. Mid acquisition. Right after a bad quarter.

The SEC hook. Rule 206(4)-7 requires written policies and procedures reasonably designed to prevent violations, and an annual review of whether they are working. A former employee who can document that they were not, even selectively and out of context, has handed an examiner a map.

The defense. Build a compliance debrief into offboarding. What did this person know. What did they have access to. What open items might they reference. Document it. If real gaps exist that a departing employee knows about, remediate them before the complaint arrives, not after.

Case 02 — The Recruited Hacker: an incident log

Drawn from real incidents. Firm and individual names have been changed.

Marcus ran IT at a mid-size RIA for six years. He knew the network better than anyone, because he built half of it. He also watched three straight years of promised equity get restructured away from him by a managing partner who drove a Porsche and expensed ski trips to the firm.

When the partners moved IT to a managed service provider, Marcus got a severance agreement and two weeks to train his replacement. He signed it. He returned his laptop. He smiled through the exit interview. Then he went home and started researching.

The research phase

Marcus was not a hacker. He knew the network topology, the Active Directory structure, and which systems held what. He had no offensive toolkit and no idea how to use one. What he had was Google and a grievance that had hardened into something focused.

He started where most people start. YouTube. Reddit. A few searches. He was not looking for a tutorial. He was looking for someone who already knew how to do what he wanted done. He wanted the client data exfiltrated and handed to a competitor. Maybe a ransomware event. Something expensive and embarrassing that traced back, in his mind, to the partners’ own negligence.

Within a few hours he found references to Tor and the forums that live on it. By the afternoon he was reading them. Setting up his cable TV had taken longer.

The forum

The forum was not dramatic. It looked like a message board from the mid 2000s. People posted in broken English and worse Russian. There were threads selling credential dumps. Threads selling remote access to compromised machines. Threads where people advertised themselves for hire.

Marcus posted in one of those. He described what he had. VPN credentials that had not been rotated, because he checked, and his account was still live two weeks after termination. Internal network documentation he had kept on a personal drive. Detailed knowledge of where client data lived and which systems had no endpoint monitoring.

He was specific. That was his mistake. It was also his value.

He had three replies in 48 hours.

The handoff

The person he settled on moved him to an encrypted channel. They asked operational questions. What kind of VPN. MFA or just a password. Were the credentials domain joined. What was running on the endpoints. Marcus answered all of it. He did not feel interrogated. He felt like he was collaborating. Someone was finally taking his grievance seriously and doing something with it.

What Marcus did not process was what he had just done. He had handed a stranger the keys to a network serving several hundred high net worth clients. The stranger was almost certainly overseas, almost certainly running other operations at the same time, and had no interest in Marcus and his revenge. The stranger was interested in data that could be sold.

What happened next

The firm’s first signal came from a client. A retiree got a convincing email that looked like it came from his advisor, asking him to update wire instructions. He called the office to confirm. The phone number in the email was one digit off.

The firm brought in an incident response team. Forensics showed Marcus’s old VPN account had authenticated from an IP in Eastern Europe, seventeen days after his termination. The attacker moved laterally, reached the CRM, and pulled a client file with names, account numbers, Social Security numbers, and net worth figures for 340 clients.

Marcus heard nothing more from his contact. The thread was deleted. The channel went dark. He learned his own role in the breach the way the clients did. A Reg S-P notification letter telling him his personal information may have been compromised. He had been a client of the firm too. His data was in the file.

The regulatory aftermath

The firm faced a Reg S-P notification covering 340 clients, with no path to the no-harm exception once the data was on a criminal forum. The examination that followed treated the incident as evidence the firm’s compliance program was not reasonably designed under Rule 206(4)-7, citing three gaps.

  • No procedure requiring credential revocation within a set time after separation.
  • No monitoring for authentication from terminated accounts.
  • No technical boundary to limit movement from a VPN entry point.

The partners were not fined. They were put through a long compliance remediation with documented evidence. That kind of process eats management attention and consulting fees for months, during what should have been a growth period.

Marcus was referred to the FBI. Federal computer-fraud and aiding-and-abetting statutes reach more than the person at the keyboard. Handing a threat actor live credentials and network architecture can create criminal exposure even if the insider never runs the attack himself. He cooperated fully. It did not help as much as he hoped.

What the scenario teaches

  • The access window is predictable. Without a formal offboarding checklist, terminated employees keep access for days. In firms we have assessed, some kept live credentials for weeks. That is not malice. It is process failure. From the attacker’s side it is a reliable, exploitable window.
  • The insider does not need to be skilled. Marcus knew enough to be useful. The market for access as a service on criminal forums is mature. Someone with network knowledge and live credentials is valuable regardless of their own skill.
  • The motive starts as pain, not money. Marcus wanted to hurt the firm. The person who answered his post wanted to monetize it. The moment the insider makes contact, their emotional logic stops mattering. The threat actor runs their own objectives, which are almost always worse than what the insider pictured.
  • The insider becomes a victim. Worth saying in any staff training. Marcus’s own data was breached and sold on the same forums where he posted his credentials.

Case 03 — The Client Poisoning Campaign

What they do. They contact your clients directly, using the client list they walked out with.

This runs from subtle to scorched earth. Subtle is a letter to clients hinting the firm is under investigation, that accounts were mishandled, or that key people are leaving. Scorched earth is a spoofed call to clients from the firm’s own main number, impersonating the advisor and lying about account security or firm stability.

The insider version is uniquely credible. A stranger claiming your RIA is committing fraud is easy to dismiss. A caller who says I worked there four years, here is your account number, here is what your advisor told you in your last review, that is a redemption event.

Why it hurts. AUM flight does not wait for facts. Spooked clients move first and ask later. One targeted round of calls to five or six significant clients can collapse a book before you have drafted a response.

The SEC hook. Reg S-P requires you to protect client data. When a former employee weaponizes contact data they should never have retained, that becomes a Reg S-P problem for your firm, regardless of their conduct, if you cannot show reasonably designed controls over access, export, and offboarding. The examiner’s question is simple. What controls stopped them from taking the client list. And when the campaign turns to impersonating your advisors about account security, firms with covered accounts are in Reg S-ID territory. A spoofed call about a client’s account is exactly the red flag your identity theft prevention program exists to detect.

The defense. Data loss prevention on client data, with CRM access and export logging. Credential revocation tied to HR offboarding. A client communication protocol you can fire fast, so your clients hear specifics from you before the noise reaches them from anywhere else.

Case 04 — Reputation Infrastructure Attacks

What they do. They damage the firm’s online presence and professional standing, using detail only an insider has.

It runs on several surfaces at once.

  • BrokerCheck and regulatory databases. Disputed items and complaint filings can surface in due diligence searches by prospects and counterparties.
  • Google and Glassdoor. Generic negative reviews get dismissed. Reviews that name real practices, real people, and accurate operational detail do not.
  • LinkedIn and industry forums. Whisper campaigns travel fast in tight fund communities.
  • Look-alike domains. Register firmname-clients.com or a Unicode lookalike, stand up a fake portal, and phish the client list. The insider knows what your real communications look like and can copy them well.

Why it hurts. Institutional investors and large family offices run reputational due diligence before they sign. A firm trailing a cloud of negative commentary, even false commentary, does not get the meeting.

The SEC hook. Your Form ADV and your regulatory record depend on being accurate and clean. Fraudulent filings and injected complaints can create disclosure problems you did not cause and cannot quickly clear.

The defense. Alerts on the firm name, principal names, and common misspellings. Defensive registration of domain variants. Scheduled monitoring of BrokerCheck and IAPD. Know what is out there before a prospect finds it.

Case 05 — The Legal Entanglement

What they do. They file actions, liens, and claims designed not to win but to cost.

A determined insider with a little procedural knowledge can file a UCC-1 financing statement against a principal or the firm, clouding title during a raise or a real estate deal. They can file an inflated wage claim with the state labor board and trigger an audit. They can file a small claims action, or an arbitration claim dressed in investment-related allegations, because they know which words create disclosure questions.

None of this needs a lawyer. Most of it costs under 100 dollars in filing fees. The point is not to prevail. The point is cost, distraction, and disclosure.

Why it hurts. Some filings create no regulatory disclosure at all. Others, especially customer complaints, investment-related arbitration or civil actions, and liens or judgments against registered persons, can surface on Form U4, Form U5, Form ADV, BrokerCheck, or IAPD, depending on the facts. A determined insider aims for that second category. And institutional due diligence flags pending litigation automatically, disclosable or not. The real cost is not legal fees. It is the deals that quietly do not happen while the item is open.

The defense. Know your disclosure obligations before anything is filed. Keep outside counsel on call who can move fast to dismiss or expunge. The faster you resolve it, the shorter the disclosure window.

Case 06 — The Physical Access Overhang

What they do. They use credentials, keys, or codes that were never revoked.

This is the simplest vector and the most often missed. A terminated employee with a working key fob, a live VPN credential, a shared password nobody rotated, or access to a shared cloud drive can do real damage from their kitchen table weeks later.

It runs from mundane to serious. Mundane is downloading the client list at 11 p.m. the day after termination. Serious is logging into the portfolio system and changing things. Petty but effective is walking into the office after hours to tamper with files or equipment.

Why it hurts. The breach may sit undiscovered for weeks or months. By then you have a Reg S-P notification event, a possible Rule 204-2 records integrity problem, and an incident that happened on your watch no matter who caused it.

The defense. A physical and logical access checklist tied to HR offboarding. Not a policy. A checklist, signed, with timestamps. Badge deactivation, credential revocation, shared password rotation, and removal from distribution lists, all complete within hours of a separation, not days.

The common thread

Every scenario here exploits the same condition. The gap between when an employee leaves and when your firm acts like they have left.

That gap, in access revocation, data controls, client notification readiness, and regulatory monitoring, is what turns a disgruntled former employee into an existential event.

There is also a human layer. Nearly every scenario above was visible to a coworker before it became an incident. The grievance that hardened. The export at 11 p.m. The ex-employee who still badges into the building. CISA’s lifecycle puts detection before response for a reason, and the earliest indicators are behavioral, not technical. A workforce trained to recognize and report them is a detection control. A workforce trained only to spot phishing emails is not.

The good news. Every one of these attack surfaces has a defensible control under your existing regulatory framework. Rule 206(4)-7 gives you the structure. Reg S-P gives you the mandate. Rule 204-2 gives you the discipline. The question is whether your written policies, procedures, and supervisory controls reflect the actual threat, or the version someone pasted from a template seven years ago.

The one control

Terminate access on the day of separation, every time, with no exceptions and documented verification. Not a policy. A process with a timestamp and a name on it.

Everything else in your incident response plan is downstream of that one control.

If you want to know where your gaps are, we run an insider threat tabletop calibrated to your firm structure. About two hours. It produces a prioritized remediation list mapped to the rules above. MTradecraft performs the risk assessment and stands up the detection and offboarding processes that close the window these attacks depend on. Reach out at info@mtradecraft.com.

Download the full brief as a PDF (free with a BrainTrust account).

BrainTrust members: the offboarding procedure in Offboarding: The 48 Hours That Decide Whether a Departure Becomes an Incident is the working checklist for the one control above, and the Access Control and MFA Policy in the library carries the deprovisioning requirements an examiner will ask to see.

MTradecraft LLC provides cybersecurity compliance consulting for SEC-registered investment advisers, including advisers to private funds, and broker-dealers. Nothing here is legal advice.

The BrainTrust, free

This article is public. A free BrainTrust account opens every Insight, the 13 Sample Deliverables, the full Mock SEC Cyber Exam and the core compliance briefs. Name and email, no card.

Create Free Account →
Outside Testing

Want an outside test of your program? One-time engagements are available only to BrainTrust Premium members →