seclook
seclook is a security lookup CLI tool that allows you to query various security services on the fly. It is essentially a wrapper over the requests library that removes the need to manually search within Web UIs or write your own requests in Postman or cURL to query these services.
You can look up information using commands like seclook [service] [value], where the service can be virustotal, shodan, emailrep, and so on. The value is the information you're querying for and varies by service.
Installation
pip install seclook- Copy config.ini.sample from this directory and place it in
~/.seclook/config.ini - Open
~/.seclook/config.iniand add in your own API keys for the services you want to use.
Some services (e.g., GreyNoise, ThreatFox) don't require API keys, but may be rate-limited more quickly without one or have other limitations. Others (e.g., YARAify) do not need an API key at all and will not be referenced in the config file.
Usage
Basic usage of seclook is as follows:
seclook [service] [value]
For example, to look up IP 1.1.1.1 on AbuseIPDB, you'd run:
seclook abuseipdb 1.1.1.1
You can pipe the output to fx or jq for further processing:
seclook emailrep andrew@akatz.org | fx
You can grep the output for known keys to get specific information:
seclook virustotal 44d88612fea8a8f36de82e1278abb02f | grep malicious
Options
--export – Use this flag to export the results to a JSON file in your current working directory.
Supported services
You can also view supported services by passing list as the service name:
seclook list
Upgrading
To upgrade seclook to the latest version:
pip install --upgrade seclook
Contributing
If you'd like to contribute to seclook, please feel free to fork the repository, create a feature branch, and then submit a Pull Request.
License
MIT License
Contact
1 maintainer
Metadata
1 maintainer
Release files for seclook 0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| seclook-0.8.tar.gz | 7.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seclook-0.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.2 kB
Release files / seclook-0.8.tar.gz
| Download URL | seclook-0.8.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87c15222d6c81fc67bf0e5eed596ddb83d644eeb8be193cc332cb34edd778a70
|
|
BLAKE2b-256 checksum How to use checksums |
eb210119f1c6e896ecd2533eda2bf4a18f0f7415d2631015eb9905ffb25c5227
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jan 29, 2025.
Transparency logRelease files / seclook-0.8-py3-none-any.whl
| Download URL | seclook-0.8-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0bc1a66bb80f37d1863e79d63f8a6e54c018e7eeaff33073092c6c84bd3bd841
|
|
BLAKE2b-256 checksum How to use checksums |
af46f5b478970b4e89958b8620767a5b78eccf538ba358aea21467af049ba7a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Jan 29, 2025.
Transparency log
