Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/infobyte/emploleaks
An OSINT tool that helps detect members of a company with leaked credentials
https://github.com/infobyte/emploleaks
bugbounty cybersecurity leaked-secrets osint pentesting redteam
Last synced: 5 days ago
JSON representation
An OSINT tool that helps detect members of a company with leaked credentials
- Host: GitHub
- URL: https://github.com/infobyte/emploleaks
- Owner: infobyte
- Created: 2023-04-21T13:48:42.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2023-11-12T10:30:47.000Z (about 1 year ago)
- Last Synced: 2024-09-27T01:50:46.449Z (about 2 months ago)
- Topics: bugbounty, cybersecurity, leaked-secrets, osint, pentesting, redteam
- Language: Python
- Homepage: https://fardadaysec.com
- Size: 210 KB
- Stars: 519
- Watchers: 9
- Forks: 46
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# π EmploLeaks
This is a tool designed for Open Source Intelligence (OSINT) purposes, which helps to gather information about employees of a company.
## π How it Works
The tool starts by searching through LinkedIn to obtain a list of employees of the company. Then, it looks for their social network profiles to find their personal email addresses. Finally, it uses those email addresses to search through a custom COMB database to retrieve leaked passwords. You an easily add yours and connect to through the tool.
## π» Installation
To use this tool, you'll need to have Python 3.10 installed on your machine. Clone this repository to your local machine and install the required dependencies using pip in the *cli* folder:
```
cd cli
pip install -r requirements.txt
```
### OSX
We know that there is a problem when installing the tool due to the *psycopg2* binary. If you run into this problem, you can solve it running:
```
cd cli
python3 -m pip install psycopg2-binary`
```
## π Basic Usage
To use the tool, simply run the following command:
python3 cli/emploleaks.py
If everything went well during the installation, you will be able to start using EmploLeaks:
```
___________ .__ .__ __
\_ _____/ _____ ______ | | ____ | | ____ _____ | | __ ______
| __)_ / \____ \| | / _ \| | _/ __ \__ \ | |/ / / ___/
| \ Y Y \ |_> > |_( <_> ) |_\ ___/ / __ \| < \___ \
/_______ /__|_| / __/|____/\____/|____/\___ >____ /__|_ \/____ >
\/ \/|__| \/ \/ \/ \/
OSINT tool π΅ to chain multiple apis
emploleaks>
```
Right now, the tool supports two functionalities:
- Linkedin, for searching all employees from a company and get their personal emails.
- A GitLab extension, which is capable of finding personal code repositories from the employees.
- If defined and connected, when the tool is gathering employees profiles, a search to a COMB database will be made in order to retrieve leaked passwords.
### Retrieving Linkedin Profiles
First, you must set the plugin to use, which in this case is *linkedin*. After, you should set your authentication tokens and the run the *impersonate* process:
```
emploleaks> use --plugin linkedin
emploleaks(linkedin)> setopt JSESSIONID
JSESSIONID:
[+] Updating value successfull
emploleaks(linkedin)> setopt li-at
li-at:
[+] Updating value successfull
emploleaks(linkedin)> show options
Module options:
Name Current Setting Required Description
---------- ----------------------------------- ---------- -----------------------------------
hide yes no hide the JSESSIONID field
JSESSIONID ************************** no active cookie session in browser #1
li-at AQEDAQ74B0YEUS-_AAABilIFFBsAAAGKdhG no active cookie session in browser #1
YG00AxGP34jz1bRrgAcxkXm9RPNeYIAXz3M
cycrQm5FB6lJ-Tezn8GGAsnl_GRpEANRdPI
lWTRJJGF9vbv5yZHKOeze_WCHoOpe4ylvET
kyCyfN58SNNH
emploleaks(linkedin)> run impersonate
[+] Using cookies from the browser
Setting for first time JSESSIONID
Setting for first time li_at
```
li\_at and JSESSIONID are the authentication cookies of your LinkedIn session on the browser. You can use the Web Developer Tools to get it, just sign-in normally at LinkedIn and press right click and Inspect, those cookies will be in the Storage tab.
Now that the module is configured, you can run it and start gathering information from the company:
```
emploleaks(linkedin)> run find EvilCorp
β Gathering Information[+] Added 1 new names.
π» Listing profiles:
0:
full name: Joaquin Rodriguez Viruliento
profile name: joaquinrodriguezviruliento
occupation: Security Researcher at EvilCorp
public identifier: joaquinrodriguezviruliento
urn: urn:li:member:15736913
β Getting and processing contact info of "Joaquin Rodriguez Viruliento"
Contact info:
website 0. http://www.evilcorp.com
twitter 0. limpiamicerca
β Done
```
### Get Linkedin accounts + Leaked Passwords
We created a custom *workflow*, where with the information retrieved by Linkedin, we try to match employees' personal emails to potential leaked passwords. In this case, you can connect to a database (in our case we have a custom indexed COMB database) using the *connect* command, as it is shown below:
```
emploleaks(linkedin)> connect --user myuser --passwd mypass123 --dbname mydbname --host 1.2.3.4
[+] Connecting to the Leak Database...
[*] version: PostgreSQL 12.15
```
Once it's connected, you can run the *workflow*. With all the users gathered, the tool will try to search in the database if a leaked credential is affecting someone:
```
emploleaks(linkedin)> run_pyscript workflows/check_leaked_passwords.py EvilCorp
[-] Failing login... trying again!
[-] Failing login... trying again!
[+] Connected to the LinkedIn api successfull
The following command could take a couple of minutes, be patient
Listing profiles:
β Getting and processing contact info of "seΓ±or girafales"
β Getting and processing contact info of "kiko"
β Getting and processing contact info of "el chavo del 8"
[...]
[+] Password for "seΓ±or girafales" exists
[*] Email: [email protected]
+------------------+
| passwords leaked |
+------------------+
| laFQqAOSL69 |
+------------------+
```
As a conclusion, the tool will generate a console output with the following information:
- A list of employees of the company (obtained from LinkedIn)
- The social network profiles associated with each employee (obtained from email address)
- A list of leaked passwords associated with each email address.
## π° How to build the indexed COMB database
An imortant aspect of this project is the use of the indexed COMB database, to build your version you need to [download the torrent first](comb.torrent). Be careful, because the files and the indexed version downloaded requires, at least, 400 GB of disk space available.
Once the torrent has been completelly downloaded you will get a file folder as following:
```
βββ count_total.sh
βββ data
β βββ 0
β βββ 1
β β βββ 0
β β βββ 1
β β βββ 2
β β βββ 3
β β βββ 4
β β βββ 5
β β βββ 6
β β βββ 7
β β βββ 8
β β βββ 9
β β βββ a
β β βββ b
β β βββ c
β β βββ d
β β βββ e
β β βββ f
β β βββ g
β β βββ h
β β βββ i
β β βββ j
β β βββ k
β β βββ l
β β βββ m
β β βββ n
β β βββ o
β β βββ p
β β βββ q
β β βββ r
β β βββ s
β β βββ symbols
β β βββ t
```
At this point, you could import all those files with the command `create_db`:
```
emploleaks> create_db --dbname leakdb --user leakdb_user --passwd leakdb_pass --comb /home/pasta/Downloads/comb
[*] The full database occups more than 200 GB, take this in account
[*] Creating the database
ERROR: database "leakdb" already exists
ERROR: role "leakdb_user" already exists
ALTER ROLE
ALTER DATABASE
GRANT
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
ALTER SYSTEM
[+] Connecting to the Leak Database...
[+] Importing from /home/pasta/Downloads/comb/data/1/m
[+] Importing from /home/pasta/Downloads/comb/data/1/d
[+] Importing from /home/pasta/Downloads/comb/data/1/v
[+] Importing from /home/pasta/Downloads/comb/data/1/0
[+] Importing from /home/pasta/Downloads/comb/data/1/8
[+] Importing from /home/pasta/Downloads/comb/data/1/u
[+] Importing from /home/pasta/Downloads/comb/data/1/k
[+] Importing from /home/pasta/Downloads/comb/data/1/r
[+] Importing from /home/pasta/Downloads/comb/data/1/7
[+] Importing from /home/pasta/Downloads/comb/data/1/h
[+] Importing from /home/pasta/Downloads/comb/data/1/o
[+] Importing from /home/pasta/Downloads/comb/data/1/t
[+] Importing from /home/pasta/Downloads/comb/data/1/f
[+] Importing from /home/pasta/Downloads/comb/data/1/n
[+] Importing from /home/pasta/Downloads/comb/data/1/symbols
[+] Importing from /home/pasta/Downloads/comb/data/1/g
[+] Importing from /home/pasta/Downloads/comb/data/1/q
[+] Importing from /home/pasta/Downloads/comb/data/1/a
[+] Importing from /home/pasta/Downloads/comb/data/1/e
[+] Importing from /home/pasta/Downloads/comb/data/1/l
[+] Importing from /home/pasta/Downloads/comb/data/1/y
[+] Importing from /home/pasta/Downloads/comb/data/1/s
[+] Importing from /home/pasta/Downloads/comb/data/1/3
[+] Importing from /home/pasta/Downloads/comb/data/1/6
[*] Creating index...
```
The importer takes a lot of time for that reason we recommend to run it with patience.
## π Next Steps
We are integrating other public sites and applications that may offer about a leaked credential. We may not be able to see the plaintext password, but it will give an insight if the user has any compromised credential:
- Integration with Have I Been Pwned?
- Integration with Firefox Monitor
- Integration with Leak Check
- Integration with BreachAlarm
Also, we will be focusing on gathering even more information from public sources of every employee. Do you have any idea in mind? Don't hesitate to reach us:
- Javi Aguinaga: [email protected]
- Gabi Franco: [email protected]
Or you con DM at [@pastacls](https://twitter.com/pastacls) or [@gaaabifranco](https://twitter.com/gaaabifranco) on Twitter.
## π License
This tool is licensed under the MIT License. See the `LICENSE` file for more information.