Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
mukul975/detecting-business-email-compromiseEngenharia social e física

detecting-business-email-compromise

⁨Detect Business Email Compromise (BEC) fraud, where attackers impersonate⁩

v1.02 instalações+2 em 7 dias36,3 mil EstrelasApache-2.0sincronizado há 11 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/detecting-business-email-compromise

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
S5B0pq7tVI…H3lX7rAg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote70177f11…3cfca785
70177f111792…cbf13cfca7858 arquivos · ⁦13.1 KB⁩
VarreduraMédio3 achados
  • Script executável junto com a skillscripts/agent.py
  • Script executável junto com a skillscripts/process.py
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/detecting-business-email-compromise@54a7988

Este item ainda não foi escrito no seu idioma, então aparece em English.

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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosNãoNão
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/agent.py
  2. MédiaArquivo · Script executável junto com a skillscripts/process.py
  3. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v1.013 de nov. de 202654a798870177f11Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login