SealTeamTools
Intro and motivation
When I started CTFing on the reg, I quickly saw the potential of automating certain tasks that arise in many, many CTFs. It might be something as dump as opening a connection to some remote server and sending/receiving data. Or quickly converting from one format to another without having to rewrite the code every time. Another example was RSA, I wrote a small wrapper script that quickly gets me a plaintext for a given c, q,p and e.
At this point the main question that will arise is, why not use pwntools? Well, it turns out that pwntools doesn't really play well with Windows. I love my Kali as much as the next guy for a variety of tasks but I also love my Win10. So I set off to slowly recreate some of the more popular functions. Fact is, the really complex functions of pwntools are not something you encounter often which means a light version fits my purposes.
Now, my motto is Go Big or Go Home. So I decided to build a comprehensive framework for CTFing and general pentesting that covers the most frequent topics: Crypto, Web, Forensics and some misc. I do most of my reversing in IDA/gdb so that category won't be represented much, I think. Additionally I have a general and socket category, the latter to make socket interaction smoother (e.g. I struggled time and again with socket blocking, it would freeze when trying to receive data when none was available), the former aiming to perform helper tasks like transposing arrays, recognizing patterns etc.
I will use this as my MCH (Main Control Hub) for progress and as time progresses, and is permitting, build an orchestrator to bring all partial scripts under one "roof".
24.9: Rearranged file structure. Now all modules will be organized using "STTxxx.filename" where xxx is the overall structure. Makes it easier to import stuff as well.
Structure
1. General
- Pattern recognition
- Base64 --> STTUtils.StringParser
- Base32 --> STTUtils.StringParser
- Hex --> STTUtils.StringParser
- flags --> STTUtils.StringParser
- Words
- Encodings
- all bases
- rot13
- Socket --> STTSocket.STTSocket
- recvline
- recvlines
- recvutil
- sendline
3. Crypto
- AES
- CBC
- ECB
- RSA
- Factorisation
- Common modulus
- Fault
- Coppersmith
- General solve --> STTCrypto.RSASolver
- ECC
- DES
- Common ciphers
- Caesar
- Railcipher
- Vigenere
- Morse --> STTCrypto.morse
4. Web
- Flask
- Nodejs
- Handlebar
- XSS
- WAF Bypass
5. Forensics
- Images
- LSB
- MSB
- exiftool
- XOR
- Audio
6. Misc
- Pyjails
- Bashjails
- Esolangs
- Embedded files
- binwalk
- Memdumps
- Vola
- OCR
- QR --> STTUtils.utils
- Packing --> STTUtils.packing
Metadata
Release files for SealTeamTools 0.0.1
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 | |
|---|---|---|---|---|
| SealTeamTools-0.0.1.tar.gz | 11.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| SealTeamTools-0.0.1-py2-none-any.whl | Python 2 | none | any | Details |
Total release size: 27.1 kB
Release files / SealTeamTools-0.0.1.tar.gz
| Download URL | SealTeamTools-0.0.1.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45e9da8efa14c082c44191bfa5d617e747501fc05e1dff9fc43ac1ab6efec1ca
|
|
BLAKE2b-256 checksum How to use checksums |
0fd3bdc26e9a2869e6bcb323a5949208dfd9c975cff89499f18e33b22628bdba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/2.7.16
|
Release files / SealTeamTools-0.0.1-py2-none-any.whl
| Download URL | SealTeamTools-0.0.1-py2-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
d271a09e693501cb5a544314f0d70f2b1677900b33af1c65d260f922b55ab6dd
|
|
BLAKE2b-256 checksum How to use checksums |
7985bcfc9f5007308f60b6e8e3cc9307d08739d497c4969e5bcf57d7bc6eb893
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/2.7.16
|
Security for SealTeamTools 0.0.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.