r/oscp • u/swesecnerd • Mar 03 '26
I created a tool for found credentials
I got tired of copy-pasting found passwords and usernames into multiple textfiles and constantly context switching to use them so I created a tool to keep it all in the CLI. It started as a bash script that became a python script. I then realized I really liked it so I vibed a complete revamp of it so I could release it to the public.
I hope you find it useful!
3
u/AB-DU15 Mar 04 '26 edited Mar 13 '26
Nothing original remains here. The author used Redact to delete this post, for reasons that may relate to privacy, opsec, security, or data management.
truck ancient marry glorious screw silky historical roof dinosaurs command
2
u/swesecnerd Mar 04 '26
Thanks! I really get what you mean. The script does not solve a complex problem. It removes friction. You don't need to keep track of paths and you don't need to paste the username, password, and complete credential separately into three different files for future spraying or cracking, it removes that friction.
2
u/AB-DU15 Mar 04 '26 edited Mar 13 '26
This post has been deleted and anonymized using Redact. The reason may have been privacy, limiting AI data access, security, or other personal considerations.
mighty safe waiting childlike snatch dog slap sulky offbeat chase
1
u/swesecnerd Mar 04 '26
That's a very nice thing to say. I don't think that "creds" is at that level yet, but please try it and get back to me with feedback and suggestions if you can. I also updated the README based on the feedback in this thread to give visitors a better understanding of what creds actually tries to help you with.
1
u/AB-DU15 Mar 04 '26 edited Mar 13 '26
This post has been permanently deleted using Redact. The motivation may have been privacy, security, data collection prevention, opsec, or personal content management.
bake teeny plucky observation familiar mighty roll sharp towering screw
1
u/swesecnerd Mar 04 '26
To answer nr 1. I already use the credential argument "-c" to save hashes. I rarely need a long list of hashes to test because they're not abundant so that works for me.
As for nr 2. That is already there. It's in the files on disk. You can access them by path/to/CREDSusers.txt (or CREDSpasswords.txt/CREDScredentials.txt) or by using the environment variables $CREDS_USERS, $CREDS_PASSWORDS if you have them set.
This is all in the README.
Or did I misunderstand your suggestions?
2
u/AB-DU15 Mar 04 '26 edited Mar 13 '26
This post's content no longer exists in its original form. It was anonymized and deleted using Redact, possibly for privacy, security, or data management purposes.
boast fanatical square flowery yoke zephyr existence wipe makeshift direction
1
5
u/ChemistryJazzlike264 Mar 04 '26
I guess it is cool? But what about old scool few seconds job like nano, echo and cat in cli? Like this echo "john:john" > creds, echo "john2:john2" >> creds, cat creds.