Token导航 LogoToken导航

Agent Skill · 运维和基础设施

detecting-business-email-compromise-with-ai(检测商业电子邮件与 AI 的妥协)

detecting-business-email-compromise-with-ai 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

detecting-business-email-compromise-with-ai 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 2,325。

总安装 210周安装 9GitHub Stars 5,917下载 73核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:detecting-business-email-compromise-with-ai(检测商业电子邮件与 AI 的妥协)
来源仓库:https://github.com/mukul975/anthropic-cybersecurity-skills
仓库路径:skills/detecting-business-email-compromise-with-ai
安装命令:
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill detecting-business-email-compromise-with-ai
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill detecting-business-email-compromise-with-ai

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

利用 AI 模型检测高级别商业邮件欺诈,提升对无恶意载荷攻击的识别率。适用于 NLP 驱动的写作风格分析、语气异常与行为模式偏离检测。可集成 BERT 等预训练模型,准确率达 98.65% 以上。需部署 ML 推理环境与标注数据,注意模型偏见与误报风险控制。

detecting-business-email-compromise-with-ai 属于运维和基础设施类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/detecting-business-email-compromise-with-ai

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skil…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

detecting-business-email-compromise-with-ai 怎么安装?

在终端执行 npx skills add https://github.com/mukul975/anthropic-cybersecurity-skills --skill detectin…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

detecting-business-email-compromise-with-ai 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

detecting-business-email-compromise-with-ai 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

detecting-business-email-compromise-with-ai 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

detecting-business-email-compromise-with-ai 用的人多吗?

公开数据是累计安装 210 次,近一周安装 9 次,下载 73 次,GitHub 5,917 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

detecting-business-email-compromise-with-ai 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 5,917 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
detecting-business-email-compromise-with-ai

检测商业电子邮件与 AI 的妥协 · 本页

2105,917需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Detecting Business Email Compromise with AI

Overview

AI-powered BEC detection uses machine learning, NLP, and behavioral analytics to identify sophisticated impersonation attacks that contain no malicious links or attachments. Traditional rule-based filters miss these attacks because BEC relies purely on social engineering. Modern AI approaches analyze writing style, tone, vocabulary, grammatical patterns, and behavioral context to determine if an email genuinely comes from the stated sender. BERT-based models achieve 98.65% accuracy in BEC detection, and AI-enhanced platforms show a 25% increase in phishing identification over keyword-based rules.

When to Use

  • When investigating security incidents that require detecting business email compromise with ai
  • 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

  • AI-powered email security platform (Abnormal Security, Tessian, Microsoft Defender)
  • Historical email data for baseline training (minimum 30 days)
  • Integration with email platform (Microsoft 365 or Google Workspace)
  • SIEM for alert correlation and investigation
  • Understanding of BEC attack types (FBI IC3 classification)

Workflow

Step 1: Deploy AI Email Security Platform

  • Select API-based solution (Abnormal Security, Tessian, Ironscales) or enhance existing SEG
  • Connect to Microsoft Graph API or Google Workspace API
  • Allow 48-hour baseline learning period on historical email data
  • Configure integration to scan inbound, outbound, and internal email
  • Verify API permissions for message access and remediation

Step 2: Configure Behavioral Baselines

  • AI learns normal communication patterns: who emails whom, frequency, tone
  • Establish writing style profiles for each user (vocabulary, sentence structure)
  • Map typical request types per role (finance processes payments, HR handles PII)
  • Baseline email metadata: typical sending times, devices, locations
  • Flag deviations from established baselines as anomalous

Step 3: Train NLP Models for BEC Detection

  • Deploy transformer-based models (BERT, GPT) for email content analysis
  • Detect urgency and manipulation language patterns
  • Identify mismatches between sender identity and writing style
  • Analyze sentiment shifts indicating social engineering pressure
  • Classify email intent: information request, payment request, credential request

Step 4: Configure Detection Policies

  • VIP impersonation: AI compares new email against known executive communication patterns
  • Vendor impersonation: detect payment change requests from vendor lookalike domains
  • Account compromise: detect sudden changes in employee email behavior
  • Supply chain BEC: monitor for impersonation of trusted partners
  • Configure confidence thresholds for auto-block vs. warning banner vs. analyst review

Step 5: Integrate with Response Workflow

  • Auto-quarantine high-confidence BEC detections
  • Add warning banners for moderate-confidence detections
  • Route suspicious emails to SOC analyst queue for review
  • Integrate with SOAR for automated response playbooks
  • Feed BEC verdicts back into training data for model improvement

Tools & Resources

  • Abnormal Security: API-based AI email security with behavioral analysis
  • Microsoft Defender for O365: Built-in AI anti-BEC with Impostor Classifier
  • Tessian (Proofpoint): AI-powered email security with human layer protection
  • Ironscales: AI + human-in-the-loop BEC detection
  • Darktrace Email: Self-learning AI for email threat detection

Validation

  • AI detects test BEC email with no malicious indicators (pure social engineering)
  • Writing style analysis identifies impersonation of known executive
  • Behavioral baseline flags unusual payment request from compromised account
  • NLP correctly classifies urgency manipulation in test scenario
  • False positive rate below 0.05% after baseline training
  • Detection rate exceeds traditional rule-based filters by 25%+

平台分布

Codex

35.16%
按下载量换算26

Claude

27.31%
按下载量换算20

Cursor

20.6%
按下载量换算15

Gemini CLI

9.65%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills