Assemblyline-service-configextractor
ConfigExtractor is an Assemblyline service that automatically extracts malware configuration data—including C2 (command-and-control) addresses, URLs, and…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
42/100 Fair
- Maintained
- 77last commit 17 days ago
- Popular
- 176 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 108 GB minimum RAM
- GitHub stars
- 6
- Open issues
- 12
- Last commit
- 2026-11-04
- Latest release
- v4.8.0.stable0
- License
- MIT
- Activity
- rising
Checked 2 days ago - source: GitHub (CybercentreCanada/assemblyline-service-configextractor)
Resources & Compatibility
Minimum requirements: 8 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Runs within Assemblyline ConfigExtractor is an Assemblyline service, not a standalone application. It must be deployed as part of a Cybercentre Canada Assemblyline instance using the cccs/assemblyline-service-configextractor Docker image. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What types of values does the service pull from malware configurations?
It extracts configuration values such as IP addresses, URLs, and domains for various malware families.
What must the service updater match when looking for parsers?
The updater requires matches on directories containing parsers, with a CAPE source directory given as an example.
Which underlying library does the service use for configuration extraction?
It uses the ConfigExtractor Python library for analysis.
Answers sourced from github.com, hub.docker.com
Community
Collected 48 days ago - public community threads