npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-ioc-extract

v1.0.2

Published

Regex-based IOC extractor node for n8n workflows.

Readme

n8n-nodes-ioc-extract

This is an n8n community node that extracts Indicators of Compromise (IOCs) from text using regex-based pattern matching. It can identify various types of security indicators including hashes, IP addresses, URLs, domains, and email addresses.

n8n is a fair-code licensed workflow automation platform.

Installation

Follow the installation guide in the n8n community nodes documentation.

Features

The IOC Extract node can extract the following types of Indicators of Compromise:

Hashes

  • MD5: 32-character hexadecimal hashes
  • SHA1: 40-character hexadecimal hashes
  • SHA256: 64-character hexadecimal hashes

Network Indicators

  • IPv4 addresses: Standard IPv4 format (e.g., 192.168.1.1)
  • IPv6 addresses: Standard IPv6 format including compressed notation
  • URLs: HTTP and HTTPS URLs
  • Domains: Domain names (excluding those already found in URLs or emails)
  • Email addresses: Standard email format

Defang/Refang Support

  • Refang Input: Automatically converts defanged IOCs in input text to normal format for extraction
    • Handles patterns like: [.], (.), [@], [://], hxxp, hxxps, [dot], [at], [1], (1), etc.
  • Defang Output: Converts extracted IOCs to defanged format in the output
    • Converts: .[.], @[@], ://[://]

Operations

The node has one operation that extracts IOCs from input text:

  • Extract IOCs: Analyzes the input text and extracts all detected IOCs

Configuration Options

Input Text

  • Required: Yes
  • Description: The text from which to extract Indicators of Compromise

Output Mode

  • Options:
    • Single Item: Outputs all IOCs in a single item with nested structure
    • Each IOC as Item: Outputs each IOC as a separate item with value, type (singular), and category (singular) attributes
  • Default: Single Item

Refang Input

  • Type: Boolean
  • Default: false
  • Description: If enabled, refangs defanged IOCs in input text before extraction (e.g., example[.]comexample.com)

Defang Output

  • Type: Boolean
  • Default: false
  • Description: If enabled, defangs extracted IOCs in output (e.g., example.comexample[.]com)

Credentials

No credentials are required for this node.

Compatibility

This node is compatible with n8n version 1.0 and later. It uses regex-based extraction and has no external dependencies.

Usage

Example 1: Basic IOC Extraction

Input text:

Contact us at [email protected] or visit https://malicious-site.com/path
The file hash is 5d41402abc4b2a76b9719d911017c592

Output (Single Item mode):

{
  "iocs": {
    "hashes": {
      "md5s": ["5d41402abc4b2a76b9719d911017c592"],
      "sha1s": [],
      "sha256s": []
    },
    "networks": {
      "ipv4s": [],
      "ipv6s": [],
      "urls": ["https://malicious-site.com/path"],
      "domains": ["example.com"],
      "emails": ["[email protected]"]
    }
  }
}

Example 2: Handling Defanged IOCs

Input text:

Visit example[.]com or contact user[@]example[.]com
IP address: 192.168.1.[1]

With "Refang Input" enabled, the node will:

  1. Convert example[.]comexample.com
  2. Convert user[@]example[.]com[email protected]
  3. Convert 192.168.1.[1]192.168.1.1
  4. Extract the IOCs from the refanged text

Example 3: Individual Item Output

With "Each IOC as Item" mode enabled, each IOC is output as a separate item:

[
  {
    "value": "[email protected]",
    "type": "email",
    "category": "network"
  },
  {
    "value": "https://malicious-site.com/path",
    "type": "url",
    "category": "network"
  },
  {
    "value": "5d41402abc4b2a76b9719d911017c592",
    "type": "md5",
    "category": "hash"
  }
]

Resources

Version history

Version 1.0.0

  • Initial release
  • Regex-based IOC extraction for hashes (MD5, SHA1, SHA256), IP addresses (IPv4, IPv6), URLs, domains, and emails
  • Support for defang/refang operations
  • Single item and individual item output modes