Find Sensitive Data’s using via network analysis make me 250$

Hello Researchers this is praveenarsh again come with my findings. Hope my every writeups will give you some new knowledge

Now a days api keys is everywhere to run web app techy.. that’s why most of the API keys and tokens leaks in public or unsecure i think :) Fun…..

But most of the API ,sensitive tokens and the credentials passed via the JS files nowadays. soo here a way to find a that type of credentials using developer tool .be loyal (am also read about it somewhere)

OK lets start, let assume my target as http://test.com/, JS files also important but instead of collecting JS files , it is a easy way to find credentials. even truffehog (extension) also sometimes missing to find these api parameters.

• Load your target.com in chrome → open inspect → go to the “Network tab” , here you can see the files which used to load a web app, enable regex(search bar) option in chrome if you didn’t set.
• In a search bar type : (api , token ,username , password)etc . just recon your domain and analyse what type of technologies they use if they use AWS technologies then change the searching keywords “ AWS” , “bucket” “aws_secret” “instance” like this.
• you can use these keywords:
• (access_key|access_token|admin_pass|admin_user|algolia_admin_key|algolia_api_key|alias_pass|alicloud_access_key|amazon_secret_access_key|amazonaws|ansible_vault_password|aos_key|api_key|api_key_secret|api_key_sid|api_secret|api.googlemaps AIza|apidocs|apikey|apiSecret|app_debug|app_id|app_key|app_log_level|app_secret|appkey|appkeysecret|application_key|appsecret|appspot|auth_token|authorizationToken|authsecret|aws_access|aws_access_key_id|aws_bucket|aws_key|aws_secret|aws_secret_key|aws_token|AWSSecretKey|b2_app_key|bashrc password|bintray_apikey|bintray_gpg_password|bintray_key|bintraykey|bluemix_api_key|bluemix_pass|browserstack_access_key|bucket_password|bucketeer_aws_access_key_id|bucketeer_aws_secret_access_key|built_branch_deploy_key|bx_password|cache_driver|cache_s3_secret_key|cattle_access_key|cattle_secret_key|certificate_password|ci_deploy_password|client_secret|client_zpk_secret_key|clojars_password|cloud_api_key|cloud_watch_aws_access_key|cloudant_password|cloudflare_api_key|cloudflare_auth_key|cloudinary_api_secret|cloudinary_name|codecov_token|config|conn.login|connectionstring|consumer_key|consumer_secret|credentials|cypress_record_key|database_password|database_schema_test|datadog_api_key|datadog_app_key|db_password|db_server|db_username|dbpasswd|dbpassword|dbuser|deploy_password|digitalocean_ssh_key_body|digitalocean_ssh_key_ids|docker_hub_password|docker_key|docker_pass|docker_passwd|docker_password|apikey|dockerhub_password|dockerhubpassword|dot-files|dotfiles|droplet_travis_password|dynamoaccesskeyid|dynamosecretaccesskey|elastica_host|elastica_port|elasticsearch_password|encryption_key|encryption_password|heroku_api_key|sonatype_password|awssecretkey)

• In my target using AWS service soo tried to keyword’ “AWS” and “ tokens” got some juicy tokens and data’s in response.

Reported: 20/06/2024

Response: 22/6/2024

Triaged : 24/06/2024

And got some juicy dollars…

Touch with via Instagram: @cybersec_praveenarsh