Supply a list of dorks and, optionally, one of the following: a user (-u) a file with a list of users (-uf) an organization (-org) a file with a list of organizations (-of) a repo (-r) You can also pass: an output directory (https://www.kitploit.com/search/label/Directory) to store results (-o) a filename to store valid items, if your users or org file may contain nonexistent users/orgs (-vif) All input files (dorks, users, or orgs) should be newline-separated.
Usage Clone the repository, then run pip install -r requirements.txt The only required parameter is the dorks file (-d). See techguan's github-dorks.txt (https://github.com/techgaun/github-dorks/blob/master/github-dorks.txt) for ideas. If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced. If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a --valid-items-filename (-vif). This will filter out any invalid users/orgs when searching for the first dork, and avoid searching against them for subsequent dorks. The output file can also then be used as the input users/orgs file to speed up later script runs. Example usage: python gh-dork.py -d dorks.txt # Basic usage
python gh-dork.py -d dorks.txt -u molly # Search repos of a specific user
python gh-dork.py -d dorks.txt -uf users.txt # Search repos of all users in the list
python gh-dork.py -d dorks.txt -uf users.txt -vif valid_users.txt # Search repos of all users in the list, filtering out nonexistent users
python gh-dork.py -d dorks.txt -org github # Search repos of a specific organization
python gh-dork.py -d dorks.txt -of orgs.txt # Search repos of all orgs in the list
python gh-dork.py -d dorks.txt -of orgs.txt -vif valid_orgs.txt # Search repos of all orgs in the list, filtering out nonexistent orgs
pyth on gh-dork.py -d dorks.txt -r molly/gh-dork # Search the specified repo
python gh-dork.py -d dorks.txt -o results # Store results in files in the results/ directory, *overwriting any directory contents*
Authentication Authentication is done with environment variables. You can authenticate with a Github private access token (https://www.kitploit.com/search/label/Access%20Token) (GH_TOKEN), or username and password (GH_USER and GH_PASS). If you have two-factor (https://www.kitploit.com/search/label/Two-Factor) authentication (https://www.kitploit.com/search/label/Authentication) enabled, you will be prompted for a two-factor code. You can also pass a Github Enterprise base URL (GH_URL) to search against that Github instance; if omitted, this will run against github.com. If no credentials (https://www.kitploit.com/search/label/Credentials) are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits (https://docs.github.com/en/rest/reference/search) for unauthenticated users. Credits Loosely based on techgaun/github-dorks (https://github.com/techgaun/github-dorks).
Download Gh-Dork (https://github.com/molly/gh-dork)
Usage Clone the repository, then run pip install -r requirements.txt The only required parameter is the dorks file (-d). See techguan's github-dorks.txt (https://github.com/techgaun/github-dorks/blob/master/github-dorks.txt) for ideas. If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced. If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a --valid-items-filename (-vif). This will filter out any invalid users/orgs when searching for the first dork, and avoid searching against them for subsequent dorks. The output file can also then be used as the input users/orgs file to speed up later script runs. Example usage: python gh-dork.py -d dorks.txt # Basic usage
python gh-dork.py -d dorks.txt -u molly # Search repos of a specific user
python gh-dork.py -d dorks.txt -uf users.txt # Search repos of all users in the list
python gh-dork.py -d dorks.txt -uf users.txt -vif valid_users.txt # Search repos of all users in the list, filtering out nonexistent users
python gh-dork.py -d dorks.txt -org github # Search repos of a specific organization
python gh-dork.py -d dorks.txt -of orgs.txt # Search repos of all orgs in the list
python gh-dork.py -d dorks.txt -of orgs.txt -vif valid_orgs.txt # Search repos of all orgs in the list, filtering out nonexistent orgs
pyth on gh-dork.py -d dorks.txt -r molly/gh-dork # Search the specified repo
python gh-dork.py -d dorks.txt -o results # Store results in files in the results/ directory, *overwriting any directory contents*
Authentication Authentication is done with environment variables. You can authenticate with a Github private access token (https://www.kitploit.com/search/label/Access%20Token) (GH_TOKEN), or username and password (GH_USER and GH_PASS). If you have two-factor (https://www.kitploit.com/search/label/Two-Factor) authentication (https://www.kitploit.com/search/label/Authentication) enabled, you will be prompted for a two-factor code. You can also pass a Github Enterprise base URL (GH_URL) to search against that Github instance; if omitted, this will run against github.com. If no credentials (https://www.kitploit.com/search/label/Credentials) are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits (https://docs.github.com/en/rest/reference/search) for unauthenticated users. Credits Loosely based on techgaun/github-dorks (https://github.com/techgaun/github-dorks).
Download Gh-Dork (https://github.com/molly/gh-dork)
Hacking Articles Tips Tricks Videos Tutorials
Photo
KitPloit - PenTest Tools!
Gh-Dork - Github Dorking Tool
https://blogger.googleusercontent.com/img/a/AVvXsEgzWtLotPeSL0AYg1-D5d_TytFdd4y03vIIl33p9-ra7Zw2RQ1AEi7sLvUeNZPKh9maTbUPAOjIFmdIt9qOIrlcrhpNhH4Du-OnmNrNz9Tu_SFpT7IkxkDg6Qzu63zWkEjxqLYeS_D8zmuEYuuGNEoPkkZLs8vOmAekB8TOtpX_ycrTDlMXPriuH6At=w640-h286 Supply a list of dorks and, optionally, one of the following:
* a user (
* a file with a list of users (
* an organization (
* a file with a list of organizations (
* a repo (
You can also pass:
* an output directory to store results (
* a filename to store valid items, if your users or org file may contain nonexistent users/orgs (
All input files (dorks, users, or orgs) should be newline-separated. UsageClone the repository, then run
If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced.
If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a
Example usage:
You can also pass a Github Enterprise base URL (
If no credentials are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits for unauthenticated users. CreditsLoosely based on techgaun/github-dorks. Download Gh-Dork
Gh-Dork - Github Dorking Tool
https://blogger.googleusercontent.com/img/a/AVvXsEgzWtLotPeSL0AYg1-D5d_TytFdd4y03vIIl33p9-ra7Zw2RQ1AEi7sLvUeNZPKh9maTbUPAOjIFmdIt9qOIrlcrhpNhH4Du-OnmNrNz9Tu_SFpT7IkxkDg6Qzu63zWkEjxqLYeS_D8zmuEYuuGNEoPkkZLs8vOmAekB8TOtpX_ycrTDlMXPriuH6At=w640-h286 Supply a list of dorks and, optionally, one of the following:
* a user (
-u)* a file with a list of users (
-uf)* an organization (
-org)* a file with a list of organizations (
-of)* a repo (
-r)You can also pass:
* an output directory to store results (
-o)* a filename to store valid items, if your users or org file may contain nonexistent users/orgs (
-vif)All input files (dorks, users, or orgs) should be newline-separated. UsageClone the repository, then run
pip install -r requirements.txtThe only required parameter is the dorks file (-d). See techguan's github-dorks.txt for ideas.If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced.
If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a
--valid-items-filename(-vif). This will filter out any invalid users/orgs when searching for the first dork, and avoid searching against them for subsequent dorks. The output file can also then be used as the input users/orgs file to speed up later script runs.Example usage:
python gh-dork.py -d dorks.txt # Basic usage
python gh-dork.py -d dorks.txt -u molly # Search repos of a specific user
python gh-dork.py -d dorks.txt -uf users.txt # Search repos of all users in the list
python gh-dork.py -d dorks.txt -uf users.txt -vif valid_users.txt # Search repos of all users in the list, filtering out nonexistent users
python gh-dork.py -d dorks.txt -org github # Search repos of a specific organization
python gh-dork.py -d dorks.txt -of orgs.txt # Search repos of all orgs in the list
python gh-dork.py -d dorks.txt -of orgs.txt -vif valid_orgs.txt # Search repos of all orgs in the list, filtering out nonexistent orgs
pyth on gh-dork.py -d dorks.txt -r molly/gh-dork # Search the specified repo
python gh-dork.py -d dorks.txt -o results # Store results in files in the results/ directory, *overwriting any directory contents* AuthenticationAuthentication is done with environment variables. You can authenticate with a Github private access token (GH_TOKEN), or username and password (GH_USER and GH_PASS). If you have two-factor authentication enabled, you will be prompted for a two-factor code.You can also pass a Github Enterprise base URL (
GH_URL) to search against that Github instance; if omitted, this will run against github.com.If no credentials are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits for unauthenticated users. CreditsLoosely based on techgaun/github-dorks. Download Gh-Dork
Gh-Dork - Github Dorking Tool
Supply a list of dorks and, optionally, one of the following: a user (-u) a file with a list of users (-uf) an organization (-org) a file with a list of organizations (-of) a repo (-r) You can also pass: an output directory to store results (-o) a filename to store valid items, if your users or org file may contain nonexistent users/orgs (-vif) All input files (dorks, users, or orgs) should be newline-separated. Usage Clone the repository, then run pip install -r requirements.txt The only required parameter is the dorks file (-d). See techguan's github-dorks.txt for ideas. If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced. If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a --valid-items-filename (-vif). This will filter out any invalid users/orgs when searching for the first dork, and avoid searching against them for subsequent dorks. The output file can also then be used as the input users/orgs file to speed up later script runs. Example usage: python gh-dork.py -d dorks.txt # Basic usagepython gh-dork.py -d dorks.txt -u molly # Search repos of a specific userpython gh-dork.py -d dorks.txt -uf users.txt # Search repos of all users in the listpython gh-dork.py -d dorks.txt -uf users.txt -vif valid_users.txt # Search repos of all users in the list, filtering out nonexistent userspython gh-dork.py -d dorks.txt -org github # Search repos of a specific organizationpython gh-dork.py -d dorks.txt -of orgs.txt # Search repos of all orgs in the listpython gh-dork.py -d dorks.txt -of orgs.txt -vif valid_orgs.txt # Search repos of all orgs in the list, filtering out nonexistent orgspyth on gh-dork.py -d dorks.txt -r molly/gh-dork # Search the specified repopython gh-dork.py -d dorks.txt -o results # Store results in files in the results/ directory, *overwriting any directory contents* Authentication Authentication is done with environment variables. You can authenticate with a Github private access token (GHTOKEN), or username and password (GHUSER and GHPASS). If you have two-factor authentication enabled, you will be prompted for a two-factor code. You can also pass a Github Enterprise base URL (GHURL) to search against that Github instance; if omitted, this will run against github.com. If no credentials are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits for unauthenticated users. Credits Loosely based on techgaun/github-dorks. Download Gh-Dork
Read more...
Supply a list of dorks and, optionally, one of the following: a user (-u) a file with a list of users (-uf) an organization (-org) a file with a list of organizations (-of) a repo (-r) You can also pass: an output directory to store results (-o) a filename to store valid items, if your users or org file may contain nonexistent users/orgs (-vif) All input files (dorks, users, or orgs) should be newline-separated. Usage Clone the repository, then run pip install -r requirements.txt The only required parameter is the dorks file (-d). See techguan's github-dorks.txt for ideas. If an output directory is specified, a file will be created for each dork in the dorks list, and results will be saved there as well as printed. Only use an empty/nonexistent directory or it will be cleared and its contents replaced. If your users or orgs files haven't already been filtered to remove non-existent users/orgs or those without any public code, it's highly recommended that you pass in a --valid-items-filename (-vif). This will filter out any invalid users/orgs when searching for the first dork, and avoid searching against them for subsequent dorks. The output file can also then be used as the input users/orgs file to speed up later script runs. Example usage: python gh-dork.py -d dorks.txt # Basic usagepython gh-dork.py -d dorks.txt -u molly # Search repos of a specific userpython gh-dork.py -d dorks.txt -uf users.txt # Search repos of all users in the listpython gh-dork.py -d dorks.txt -uf users.txt -vif valid_users.txt # Search repos of all users in the list, filtering out nonexistent userspython gh-dork.py -d dorks.txt -org github # Search repos of a specific organizationpython gh-dork.py -d dorks.txt -of orgs.txt # Search repos of all orgs in the listpython gh-dork.py -d dorks.txt -of orgs.txt -vif valid_orgs.txt # Search repos of all orgs in the list, filtering out nonexistent orgspyth on gh-dork.py -d dorks.txt -r molly/gh-dork # Search the specified repopython gh-dork.py -d dorks.txt -o results # Store results in files in the results/ directory, *overwriting any directory contents* Authentication Authentication is done with environment variables. You can authenticate with a Github private access token (GHTOKEN), or username and password (GHUSER and GHPASS). If you have two-factor authentication enabled, you will be prompted for a two-factor code. You can also pass a Github Enterprise base URL (GHURL) to search against that Github instance; if omitted, this will run against github.com. If no credentials are provided or if credentials are invalid, the script will still run, but will be limited by the much lower rate limits for unauthenticated users. Credits Loosely based on techgaun/github-dorks. Download Gh-Dork
Read more...
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
7 Ways to Protect Your Crypto Wallet from Hackers.
https://cdn-images-1.medium.com/max/1000/1*D-no6c2TbJPEFPasz5BBtQ.jpeg
1. Enable two-factor authentication
Having two-factor authentication enabled is one of the best ways to protect your crypto wallet. It…
Continue reading on Medium »
7 Ways to Protect Your Crypto Wallet from Hackers.
https://cdn-images-1.medium.com/max/1000/1*D-no6c2TbJPEFPasz5BBtQ.jpeg
1. Enable two-factor authentication
Having two-factor authentication enabled is one of the best ways to protect your crypto wallet. It…
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
CSRF attack for beginners
https://cdn-images-1.medium.com/max/711/1*5eFvD3up96eYBqy510apYw.png
CSRF is an abbreviation for Cross-Site Request Forgery where the attacker induces the user to perform malicious activities in the web…
Continue reading on Medium »
CSRF attack for beginners
https://cdn-images-1.medium.com/max/711/1*5eFvD3up96eYBqy510apYw.png
CSRF is an abbreviation for Cross-Site Request Forgery where the attacker induces the user to perform malicious activities in the web…
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
“Previse — Hack_The_Box”
https://cdn-images-1.medium.com/max/1019/1*H3ruI3FLBAxhP3xfKHk6BQ.png
Hello everyone, In this blog post I am will be explaining how I was able to get root shell on this machine.
Continue reading on Medium »
“Previse — Hack_The_Box”
https://cdn-images-1.medium.com/max/1019/1*H3ruI3FLBAxhP3xfKHk6BQ.png
Hello everyone, In this blog post I am will be explaining how I was able to get root shell on this machine.
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
Extremely Easy Security — Learn Cyber Attack Types in Plain English (1.2 Part 1)
https://cdn-images-1.medium.com/max/749/1*Iqdcd4zSDFBRfMW8IlaIcw.png
Today we will be covering different types of cyberattacks and the indicators you can look for to find them, as well as the remediation…
Continue reading on Medium »
Extremely Easy Security — Learn Cyber Attack Types in Plain English (1.2 Part 1)
https://cdn-images-1.medium.com/max/749/1*Iqdcd4zSDFBRfMW8IlaIcw.png
Today we will be covering different types of cyberattacks and the indicators you can look for to find them, as well as the remediation…
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
Termux Instagram Infoga : Gather Instagram info with Termux
https://cdn-images-1.medium.com/max/600/0*UYN3PcHMDB_Eifzj
Hey Guys🙋♂️, , it takes Instagram is one of the most widely used more than an hour to figure out about someone’s most used tags and who…
Continue reading on Medium »
Termux Instagram Infoga : Gather Instagram info with Termux
https://cdn-images-1.medium.com/max/600/0*UYN3PcHMDB_Eifzj
Hey Guys🙋♂️, , it takes Instagram is one of the most widely used more than an hour to figure out about someone’s most used tags and who…
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking on Medium
Piratas informáticos utilizan una nueva técnica evasiva para entregar el malware AsyncRAT
https://cdn-images-1.medium.com/max/1523/0*L99BDHKEsZQ4_5pA
PUBLICADO EN 27 ENERO, 2022POR EHACKING
Continue reading on Medium »
Piratas informáticos utilizan una nueva técnica evasiva para entregar el malware AsyncRAT
https://cdn-images-1.medium.com/max/1523/0*L99BDHKEsZQ4_5pA
PUBLICADO EN 27 ENERO, 2022POR EHACKING
Continue reading on Medium »
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking Articles
Domain Persistence: Golden Certificate Attack
IntroductionSecurity analysts who have some knowledge about Active Directory and pentesting would know the concept of tickets. Kerberos, the default authentication mechanism in an AD, uses ticket-based authentication where a Key Distribution Center (KDC) grants a Ticket-Granting Ticket (TGT) to a user requesting access to a service or an account which can then be redeemed to generate a service ticket (ST) to access a particular service, like SQL account. Attacks such as Golden Ticket demonstrate how an attacker can persist its access to the domain admin by obtaining the “krbtgt” account’s NTLM hash. Domain persistence is necessary for an analyst in the event the admin password gets changed. Persistence can also be achieved by using certificate-based authentication deployed in Active Directory Certificate Service. One such method is the Golden Certificate Attack. This technique leverages the certificate-based authentication in AD enabled by default with the installation of ADCS (Active Directory Certificate Services) by forging a new certificate using the private key of the CA certificate. The technique was implemented by Benjamin Delpy in Mimikatz. Will Schroeder and Lee Christensen wrote a research paper on this technique which can be referred to here. Table of Content* ADCS and Certificate Basics
* Installing ADCS in a local AD environment
* Extracting CA certificate
* Forging a new CA certificate
* Obtaining domain admin’s TGT
* Extracting admin NTLM hash
* Performing PtH (Pass the Hash) attack ADCS and Certificate BasicsADCS provides authentication in a forest. It enhances the overall security identity of a member (user or service account) by binding it to a corresponding private key. A certificate is an X.509-formatted digitally signed document used for encryption, message signing, and/or authentication. It contains the following details:
* Subject – The owner of the certificate.
* Public Key – Associates the Subject with a private key stored separately.
* NotBefore and NotAfter dates – Define the duration that the certificate is valid.
* Serial Number – An identifier for the certificate assigned by the CA.
* Issuer – Identifies who issued the certificate (commonly a CA).
* SubjectAlternativeName – Defines one or more alternate names that the Subject may go by.
* Basic Constraints – Identifies if the certificate is a CA or an end entity and if there are any constraints when using the certificate.
* Extended Key Usages (EKUs) – Object identifiers (OIDs) that describe how the certificate will be used. Also known as Enhanced Key Usage in Microsoft parlance
* Signature Algorithm – Specifies the algorithm used to sign the certificate.
* Signature – The signature of the certificates body is made using the issuer’s (e.g., a CA’s) private key.
Certificate Authorities (CAs) are responsible for issuing certificates. Upon ADCS installation, CA first creates its own public-private key pair and signs its own root CA using its private key. Hosts add this root CA in their systems to build a trust system.
Certificate Enrollment – The process of a client obtaining a certificate from AD CS is called certificate enrolment in which the following steps happen:
* Client generates public/private key pair
* Client places a public key in a Certificate Signing Request which includes details like the subject of certificate and certificate template name.
* Clients sign CSR using the private key and send CSR to the enterprise CA server.
* CA server verifies the client’s requested certificate’s template
* CA generates the certificate and signs it using its own private key
Types of extensions in certificates – Following extensions can be found throughout this article:
* *.p12 – The PKCS#12 is a binary format for storing the[...]
Domain Persistence: Golden Certificate Attack
IntroductionSecurity analysts who have some knowledge about Active Directory and pentesting would know the concept of tickets. Kerberos, the default authentication mechanism in an AD, uses ticket-based authentication where a Key Distribution Center (KDC) grants a Ticket-Granting Ticket (TGT) to a user requesting access to a service or an account which can then be redeemed to generate a service ticket (ST) to access a particular service, like SQL account. Attacks such as Golden Ticket demonstrate how an attacker can persist its access to the domain admin by obtaining the “krbtgt” account’s NTLM hash. Domain persistence is necessary for an analyst in the event the admin password gets changed. Persistence can also be achieved by using certificate-based authentication deployed in Active Directory Certificate Service. One such method is the Golden Certificate Attack. This technique leverages the certificate-based authentication in AD enabled by default with the installation of ADCS (Active Directory Certificate Services) by forging a new certificate using the private key of the CA certificate. The technique was implemented by Benjamin Delpy in Mimikatz. Will Schroeder and Lee Christensen wrote a research paper on this technique which can be referred to here. Table of Content* ADCS and Certificate Basics
* Installing ADCS in a local AD environment
* Extracting CA certificate
* Forging a new CA certificate
* Obtaining domain admin’s TGT
* Extracting admin NTLM hash
* Performing PtH (Pass the Hash) attack ADCS and Certificate BasicsADCS provides authentication in a forest. It enhances the overall security identity of a member (user or service account) by binding it to a corresponding private key. A certificate is an X.509-formatted digitally signed document used for encryption, message signing, and/or authentication. It contains the following details:
* Subject – The owner of the certificate.
* Public Key – Associates the Subject with a private key stored separately.
* NotBefore and NotAfter dates – Define the duration that the certificate is valid.
* Serial Number – An identifier for the certificate assigned by the CA.
* Issuer – Identifies who issued the certificate (commonly a CA).
* SubjectAlternativeName – Defines one or more alternate names that the Subject may go by.
* Basic Constraints – Identifies if the certificate is a CA or an end entity and if there are any constraints when using the certificate.
* Extended Key Usages (EKUs) – Object identifiers (OIDs) that describe how the certificate will be used. Also known as Enhanced Key Usage in Microsoft parlance
* Signature Algorithm – Specifies the algorithm used to sign the certificate.
* Signature – The signature of the certificates body is made using the issuer’s (e.g., a CA’s) private key.
Certificate Authorities (CAs) are responsible for issuing certificates. Upon ADCS installation, CA first creates its own public-private key pair and signs its own root CA using its private key. Hosts add this root CA in their systems to build a trust system.
Certificate Enrollment – The process of a client obtaining a certificate from AD CS is called certificate enrolment in which the following steps happen:
* Client generates public/private key pair
* Client places a public key in a Certificate Signing Request which includes details like the subject of certificate and certificate template name.
* Clients sign CSR using the private key and send CSR to the enterprise CA server.
* CA server verifies the client’s requested certificate’s template
* CA generates the certificate and signs it using its own private key
Types of extensions in certificates – Following extensions can be found throughout this article:
* *.p12 – The PKCS#12 is a binary format for storing the[...]