CAPE-parsers
CAPE core and community parsers
Configs structure
CNCs: []
campaign: str
botnet: str
dga_seed: hex str
version: str
mutex: str
user_agent: str
build: str
cryptokey: str
cryptokey_type: str (algorithm). Ex: RC4, RSA public key. salsa20, (x)chacha20
raw: {any other data goes here}
- All CNC entries should be in URL format. aka
<schema>://<hostname>:<port>/<uri>- Schema examples:
tcp://,ftp://,udp://,http(s), etc. - Old CAPE configs still have lack of this structures as most of them are dead families.
- This CNC simplification make it easier to parse with tools like
tldextractorurlparse
- Schema examples:
1 maintainer
Metadata
1 maintainer
Release files for CAPE-parsers 0.1.73
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cape_parsers-0.1.73.tar.gz | 161.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cape_parsers-0.1.73-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 379.8 kB
Release files / cape_parsers-0.1.73.tar.gz
| Download URL | cape_parsers-0.1.73.tar.gz |
|---|---|
| Size | 161.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e74e400bf10b38e2c07e333b8908ac68d05a3b8a7c98bd23102a8a8815850022
|
|
BLAKE2b-256 checksum How to use checksums |
1ba7da6ba078cf6eb4394c3eae72d6b89b330cfd32d6edb4e3f77c42602d4f4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / cape_parsers-0.1.73-py3-none-any.whl
| Download URL | cape_parsers-0.1.73-py3-none-any.whl |
|---|---|
| Size | 218.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f343207fba42abf48fd8a3dfcea20a2ac74fc62af3acd371de115032517b903e
|
|
BLAKE2b-256 checksum How to use checksums |
7362fb364e20d3cba8dc513f577c06e8c60e38e2a88dda300e89e17d7aedf436
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for CAPE-parsers 0.1.73
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cape_parsers-0.1.73.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
