Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
meltedinhex/enriching-iocs-with-threat-intel-sourcesAnálisis de malware y ransomware

enriching-iocs-with-threat-intel-sources

⁨Enriches indicators with context from threat-intel sources: planning lookups against⁩

v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/enriching-iocs-with-threat-intel-sources

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
nX2SZGDT4Y…WWHU6xDg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete0701b45f…f8c9142f
0701b45f781d…8532f8c9142f4 archivos · ⁦3.0 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/enriching-iocs-with-threat-intel-sources@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When to Use

  • You have atomic indicators and need context: reputation, related infrastructure, first/last seen, and known associations.
  • You are scoring indicator confidence before acting or reporting.
  • You must plan lookups without leaking your investigation to the adversary.

Do not use active interaction (visiting a C2 URL, resolving a live domain from your own network) for enrichment — use passive sources to avoid tipping off the adversary.

Prerequisites

  • Defanged indicators (from the defanging skill) and access to enrichment sources/APIs.
  • Awareness of each source's operational-security implications.

Safety & Handling

  • Prefer passive sources (passive DNS, sample DBs, reputation feeds) over active probing.
  • Never submit a customer/internal sample to a public sandbox without authorization — it becomes publicly retrievable and can expose sensitive data.

Workflow

Step 1: Group indicators by type

Separate hashes, domains, IPs, and URLs; each maps to different enrichment sources.

Step 2: Plan the right lookups

Map each type to passive sources: hashes → sample/AV databases; domains → passive DNS, WHOIS, reputation; IPs → ASN/geo, passive DNS, reputation; URLs → URL reputation/sandbox history.

bash
python scripts/analyst.py plan iocs.json

Step 3: Score confidence

Combine source agreement, age, and prevalence into a confidence score; a single hit on one feed is weaker than corroboration across independent sources.

Step 4: Annotate and pivot

Attach context (first seen, related infrastructure, family) and pivot on strong links (shared registrant, hosting, certificate) to expand the picture.

Step 5: Record provenance

Note which source provided each piece of context and when, so the enrichment is auditable and re-checkable.

Validation

  • Each indicator is routed to type-appropriate, passive sources.
  • Confidence reflects corroboration across independent sources, not a single feed.
  • Every enrichment carries source and timestamp provenance.

Pitfalls

  • Actively resolving/visiting live infrastructure and alerting the adversary.
  • Uploading sensitive samples to public services, leaking data.
  • Treating one feed's verdict as ground truth without corroboration.

References

  • See references/api-reference.md for the lookup planner.
  • MITRE ATT&CK and passive-DNS enrichment concepts (linked in frontmatter).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600a0701b45fFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login