Skip to content
cccskills
FreePublished on GitHub

detecting-business-email-compromise

Investigate business email compromise, where impersonated executives or vendors request payments or sensitive data. Check sender details, unusual communication patterns, mailbox changes, and payment approval procedures to develop detection rules and verification controls.

OriginalShow the original description

Detect Business Email Compromise (BEC) fraud, where attackers impersonate executives or vendors to trick employees into wire transfers or data disclosure without malicious links, using email gateway rules, behavioral analytics, and financial process controls. Use when investigating a suspected executive/vendor impersonation email or building detection rules for social-engineering fund-transfer fraud.

Run score Not tested

See how to install

Good for

  • Investigating emails impersonating executives or vendors
  • Reviewing requests to change vendor bank details
  • Building detection rules for fraudulent payment requests
  • Checking forwarding rules for signs of account compromise

Files included (8)

  • SKILL.md5.0 KB
  • assets/template.md1.1 KB
  • LICENSE11.0 KB
  • references/api-reference.md1.9 KB
  • references/standards.md1.4 KB
  • references/workflows.md2.3 KB
  • scripts/agent.py5.5 KB
  • scripts/process.py11.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Detecting Business Email Compromise

Overview

Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data, or changing payment details. Unlike traditional phishing, BEC often contains no malicious links or attachments, relying purely on social engineering. This skill covers detection techniques using email gateway rules, behavioral analytics, and financial process controls.

When to Use

  • When investigating security incidents that require detecting business email compromise
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Email security gateway with BEC detection capabilities
  • Understanding of organizational financial processes and approval chains
  • Access to email logs and SIEM platform
  • Knowledge of social engineering tactics

Key Concepts

BEC Attack Types (FBI IC3 Classification)

  1. CEO Fraud: Attacker impersonates CEO, requests urgent wire transfer
  2. Account Compromise: Employee email compromised, used to request payments from vendors
  3. False Invoice Scheme: Fake invoices from "vendor" with changed bank details
  4. Attorney Impersonation: Impersonates legal counsel for urgent confidential transfers
  5. Data Theft: Requests W-2, tax forms, or PII from HR

Detection Indicators

  • Urgency and secrecy language ("confidential", "do not discuss with others")
  • New or changed payment instructions
  • Executive communication outside normal patterns
  • Display name matches executive but email domain differs
  • Reply-to address differs from From address
  • First-time communication pattern between sender and recipient
  • Request for gift cards or cryptocurrency

Workflow

Step 1: Configure BEC-Specific Email Rules

  • Flag emails with VIP display names from external domains
  • Detect financial keywords combined with urgency language
  • Alert on first-time sender to finance/accounting staff
  • Check for Reply-To domain mismatch

Step 2: Deploy Behavioral Analytics

  • Baseline normal communication patterns per user
  • Detect anomalous requests (unusual recipient, unusual time, unusual request type)
  • Monitor for email forwarding rule changes (T1114.003)

Step 3: Implement Financial Controls

  • Dual-authorization for wire transfers above threshold
  • Out-of-band verification for payment detail changes (phone callback)
  • Vendor payment change verification process
  • Finance team training on BEC red flags

Step 4: Monitor for Account Compromise

  • Detect impossible travel in email login locations
  • Alert on email forwarding rule creation
  • Monitor for mailbox delegation changes
  • Check for inbox rules hiding BEC-related emails

Tools & Resources

  • Microsoft Defender for O365 Anti-BEC: Built-in BEC detection
  • Proofpoint Email Fraud Defense: BEC-specific solution
  • Abnormal Security: AI-driven BEC detection
  • FBI IC3 BEC Advisory: https://www.ic3.gov/
  • FinCEN BEC Advisory: Financial institution guidance

Validation

  • BEC detection rules trigger on test scenarios
  • Financial controls prevent unauthorized transfers in drills
  • Account compromise detection catches simulated attacks
  • Reduced BEC susceptibility in awareness assessments

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess exposure of Windows secrets protected by DPAPI, the operating system’s data protection service, during authorized security tests. Guide examination and decryption of saved credentials and browser data using available user sessions, credentials, or backup keys.

  • Assessing saved credential exposure in authorized tests
  • Examining collected DPAPI files offline
  • Reviewing protected browser and RDP credentials
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Assess Shadow Credentials account takeover during authorized Active Directory testing. Examine permissions that allow public key registration, validate authentication without a password reset, and document credential cleanup, detection opportunities, and access control changes needed for remediation.

  • Assessing risky permissions identified in BloodHound
  • Validating account takeover without resetting a password
  • Generating directory change records during security exercises
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Prepare for CMMC Level 2, a cybersecurity certification for defense contractors. Define the systems handling controlled information, review security requirements, calculate the SPRS assessment score, and organize remediation plans and evidence into a readiness report.

  • Define the assessment scope for systems handling controlled information
  • Calculate an SPRS score and prioritize unmet security requirements
  • Prepare security plans, remediation milestones, and assessment evidence
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

  • Preserving a suspect drive before investigation
  • Creating evidence copies of USB devices or memory cards
  • Verifying that a disk image matches its source
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Review Active Directory permissions with ldap3, a Python library for directory queries. Identify excessive access granted to non-administrative accounts, explain potential privilege escalation paths, and produce a JSON report with affected objects and remediation recommendations.

  • Auditing excessive Active Directory permissions
  • Investigating privilege escalation paths from ordinary accounts
  • Reporting affected objects and permission remediation recommendations
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

Inspect suspicious Android APK files without running them. Analyze permissions, app components, suspicious code patterns, and network indicators, then produce a JSON risk report to support malware triage and detection rule development.

  • Triage suspicious APK files without running them
  • Inspect dangerous permission combinations and suspicious API calls
  • Extract network indicators for malware detection rules
mukul975/Anthropic-Cybersecurity-Skills34.9KUpdated Aug 31, 2026

See all skills by mukul975

Report a problem with this skill