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
zhaoxuya520/competition-mailbox-abuseAnálise de malware e ransomware

competition-mailbox-abuse

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for enterprise mail abuse, OAuth consent, inbox or forwarding rules, transport rules, shared mailbox access, phishing chains, and token-to-mailbox side effects. Use when the user asks to trace mailbox rules, OAuth consent g⁩

v2026.9.22-cab634b3 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-mailbox-abuse

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

AssinaturaAssinado, ed25519
nUsd3bzCTb…cRB2P2Ag==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotec05120a0…cc03968d
c05120a0736f…1b2ccc03968d3 arquivos · ⁦2.0 KB⁩
VarreduraMédio1 achado
  • injection.no_confirmationreferences/mailbox-abuse.md:20
Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-mailbox-abuse@cab634b

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

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive path runs through mailbox behavior, consent flow, or message-routing effects rather than generic AD evidence alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Decide whether the active path is phishing-to-consent, token-to-mailbox, rule-based persistence, or transport-level mail rerouting.
  2. Keep mailbox evidence, identity evidence, and message-trace evidence tied to the same user, mailbox, token, or message ID.
  3. Separate possession of a token or delegate edge from the actual mailbox effect it enables.
  4. Record forwarding targets, rule predicates, consent scopes, shared mailbox edges, and resulting mail flow in compact blocks.
  5. Reproduce the smallest mail effect that proves persistence, exfiltration, or privilege.

Workflow

1. Map The Mail Trust Path

  • Identify the principal, mailbox, token or session, consent grant, delegate edge, shared mailbox relationship, or app registration involved.
  • Record consent scopes, mailbox permissions, rule ownership, transport actions, and message-trace identifiers.
  • Distinguish client-visible symptoms from server-side mailbox or transport state.

2. Prove The Mailbox Effect

  • Correlate consent logs, sign-ins, message traces, inbox rules, transport rules, forwarding settings, and mailbox audit events.
  • Show which rule or token produces which concrete effect: silent forwarding, marking read, deletion, delegate access, or message rerouting.
  • Keep message IDs, sender or recipient pairs, and timestamps aligned across logs.

3. Reduce To The Decisive Abuse Chain

  • Compress the path to the smallest sequence: lure or grant -> token or delegate edge -> mailbox or transport mutation -> resulting mail effect.
  • State clearly whether persistence lives in consent, mailbox rules, transport config, or shared mailbox permissions.
  • If the task broadens into host pivots or Kerberos acceptance, switch back to the broader identity skill.

Read This Reference

  • Load references/mailbox-abuse.md for the consent checklist, rule checklist, and evidence packaging.

What To Preserve

  • Consent scopes, token claims, mailbox permissions, rule definitions, forwarding targets, and message IDs
  • Message-trace lines, audit events, and mailbox effects tied to the same mail path
  • The smallest replayable sequence that proves persistence, exfiltration, or delegate access

Arquivos desta versão

Permissões

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

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaPrompt injection · injection.no_confirmationreferences/mailbox-abuse.md:20

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
v2026.9.22-cab634b13 de nov. de 2026cab634bc05120a0Assinada–

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