This tool lets you find the account id an S3 bucket belongs too. For this to work you need to have at least one of these permissions: Permission to download a known file from the bucket (s3:getObject). Permission to list the contents of the bucket (s3:ListBucket). Additionally, you will need a role that you can assume with (one of) these permissions on the bucket you're examining Some more background can be found on the Cloudar Blog (https://www.cloudar.be/awsblog/finding-the-accountid-of-any-public-s3-bucket/)
Installation
This package is available on pypi, you can for example use on of these commands (pipx is recommended) pipx install s3-account-search
pip install s3-account-search
Usage Examples
# with a bucket
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket

# with an object
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket/path/to/object.ext

# You can also leave out the s3://
s3-account-search arn:aws:iam::123456789012:role/s3_read my-bucket

# Or start from a specified source profile
s3-account-search --profile source_profile arn:aws:iam::123456789012:role/s3_read s3://my-bucket
How this works
There is an IAM policy condition s3:ResourceAccount, that is meant to be used to give access (https://www.kitploit.com/search/label/Access) to S3 in specified (set of) account(s), but also supports wildcards. By constructing the right patterns, and seeing which ones will lead to a Deny or an Allow, we can determine the account id by discovering it one digit at a time. We verify that we can access the object or bucket with the provided role We assume the same role again, but this time add a policy that restricts our access to S3 buckets that exist (https://www.kitploit.com/search/label/EXIST) in an account starting with 0. If our access is allowed we know that the account id has to start with 0. If the request is denied, we try again with 1 as the first digit. We keep incrementing until our request is allowed, and we find the first digit We repeat this process for every digit. Using the already discovered digits as a prefix. E.g. if the first digit was 8, we test account ids starting with 80, 81, 82, etc.
Development
We use poetry to manage this project Clone this repository Run poetry install Activate the virtualenvironment with poetry shell (you can also use poetry run $command)
Releasing a new version to pypi
Edit pyproject.toml to update the version number Commit the version number bump Run poetry publish --build Push to GitHub Create a new release in GitHub
Possible improvements
Instead of checking one digit at a time, we could use a binary (https://www.kitploit.com/search/label/Binary) search-like algorithm. Eg. the following condition is equivalent to s3:ResourceAccount < 500000000000 "Condition": {
"StringLike": {"s3:ResourceAccount": [
"0*", "1*", "2*", "3*", "4*",
]},
}, Similarly, there is a speed improvement possible by checking multiple digits per position in parallel (There is a small risk of being rate limited by STS when using this approach) In practice this tool should be fast enough in most cases.

Download S3-Account-Search (https://github.com/WeAreCloudar/s3-account-search)

hacking: security in practice
Can I use inbuilt wireless adapter for monitor mode and/or packet injection?

My laptop has a wireless adapter Qualcomm Atheros QCA61x4A that supports both 2.4 GHz and 5 GHz bands. I found out that it can't be used for Kali on virtualbox. I wanted to know if it can be used for packet injection and/or monitor mode before I actually install bare metal Kali. Thanks.

submitted by /u/jagadambachowdary
[link] [comments]

hacking: security in practice
There's new documentary on hackers and how they are the new gods. It's good to watch

https://www.youtube.com/watch?v=vyLC7wf_Sbk&t=4s

submitted by /u/Comprehensive_Cut_44
[link] [comments]

hacking: security in practice
How does a dictionary hack work when passwords are validated wholesale?

Let's say I have a password like

TextboxBoldLinkItalic24Protection

Five words, each recognizable on its own. Is this hackable, since the individual words in the password aren't validated one at a time. Seems to me that since passwords are validated all at once, this would be as effective as a random string of characters the same length.

Am I missing something?

submitted by /u/mapsedge
[link] [comments]

hacking: security in practice
Target Data Breach Cost Canadians $940M

https://external-preview.redd.it/uUSMLvvhQpsICAKv26alarHsEdp2OpnfZw5UmOPyUew.jpg?width=320&crop=smart&auto=webp&s=2eb2cb674652cd73d9eb01fc6dee63393a0fb1a4 submitted by /u/WhichCarry
[link] [comments]

hacking: security in practice
Hashcat vs hashes.com to decrypt MD5 and SHA1

I was curious about what you guys have had more success with in the past to break hashed passwords from a leak Db. Hashcat would probably be the right choice, but I'm wondering exactly how effective it would be compared to simple online tools like hashes.com which I've seen some half decent results with. Just curious, thanks!

submitted by /u/TheThomasKinley
[link] [comments]

S3-Account-Search - S3 Account Search

This tool lets you find the account id an S3 bucket belongs too. For this to work you need to have at least one of these permissions: Permission to download a known file from the bucket (s3:getObject). Permission to list the contents of the bucket (s3:ListBucket). Additionally, you will need a role that you can assume with (one of) these permissions on the bucket you're examining Some more background can be found on the Cloudar BlogInstallation This package is available on pypi, you can for example use on of these commands (pipx is recommended) pipx install s3-account-searchpip install s3-account-search Usage Examples # with a buckets3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket# with an objects3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket/path/to/object.ext# You can also leave out the s3://s3-account-search arn:aws:iam::123456789012:role/s3_read my-bucket# Or start from a specified source profiles3-account-search --profile source_profile arn:aws:iam::123456789012:role/s3_read s3://my-bucket How this works There is an IAM policy condition s3:ResourceAccount, that is meant to be used to give access to S3 in specified (set of) account(s), but also supports wildcards. By constructing the right patterns, and seeing which ones will lead to a Deny or an Allow, we can determine the account id by discovering it one digit at a time. We verify that we can access the object or bucket with the provided role We assume the same role again, but this time add a policy that restricts our access to S3 buckets that exist in an account starting with 0. If our access is allowed we know that the account id has to start with 0. If the request is denied, we try again with 1 as the first digit. We keep incrementing until our request is allowed, and we find the first digit We repeat this process for every digit. Using the already discovered digits as a prefix. E.g. if the first digit was 8, we test account ids starting with 80, 81, 82, etc. Development We use poetry to manage this project Clone this repository Run poetry install Activate the virtualenvironment with poetry shell (you can also use poetry run $command) Releasing a new version to pypi Edit pyproject.toml to update the version number Commit the version number bump Run poetry publish --build Push to GitHub Create a new release in GitHub Possible improvements Instead of checking one digit at a time, we could use a binary search-like algorithm. Eg. the following condition is equivalent to s3:ResourceAccount < 500000000000 "Condition": { "StringLike": {"s3:ResourceAccount": "0\*", "1\*", "2\*", "3\*", "4\*", },}, Similarly, there is a speed improvement possible by checking multiple digits per position in parallel (There is a small risk of being rate limited by STS when using this approach) In practice this tool should be fast enough in most cases. Download S3-Account-Search
Read more...

Dark Reading: Attacks/Breaches
Ransomware Losses Drive Up Cyber-Insurance Costs

Premiums have gone up by 7% on average for small firms and between 10% and 40% for medium and large businesses.

Hacking on Medium
Ransomware Cybersecurity Fireside Chat

https://cdn-images-1.medium.com/max/960/1*5waTP3nquL9Lh7WG-8Zx0A.png
In today’s fireside chat, we discuss the relevance, proactive, and reactive considerations every organization should consider as they face…

Continue reading on Medium »

KitPloit - PenTest Tools!
S3-Account-Search - S3 Account Search

https://1.bp.blogspot.com/-iJh19OQVUTQ/YNEo8Ei9XgI/AAAAAAAAdek/xvGi5J0VKz0IR6lwWiDqdmkJ1D470W0uACNcBGAsYHQ/w640-h220/aws_s3.png This tool lets you find the account id an S3 bucket belongs too.

For this to work you need to have at least one of these permissions:

* Permission to download a known file from the bucket (s3:getObject).
* Permission to list the contents of the bucket (s3:ListBucket).

Additionally, you will need a role that you can assume with (one of) these permissions on the bucket you're examining

Some more background can be found on the Cloudar Blog InstallationThis package is available on pypi, you can for example use on of these commands (pipx is recommended) pipx install s3-account-search
pip install s3-account-searchUsage Examples# with a bucket
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket

# with an object
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket/path/to/object.ext

# You can also leave out the s3://
s3-account-search arn:aws:iam::123456789012:role/s3_read my-bucket

# Or start from a specified source profile
s3-account-search --profile source_profile arn:aws:iam::123456789012:role/s3_read s3://my-bucketHow this worksThere is an IAM policy condition s3:ResourceAccount, that is meant to be used to give access to S3 in specified (set of) account(s), but also supports wildcards. By constructing the right patterns, and seeing which ones will lead to a Deny or an Allow, we can determine the account id by discovering it one digit at a time.

1. We verify that we can access the object or bucket with the provided role
2. We assume the same role again, but this time add a policy that restricts our access to S3 buckets that exist in an account starting with 0. If our access is allowed we know that the account id has to start with 0. If the request is denied, we try again with 1as the first digit. We keep incrementing until our request is allowed, and we find the first digit
3. We repeat this process for every digit. Using the already discovered digits as a prefix. E.g. if the first digit was 8, we test account ids starting with 80, 81, 82, etc. DevelopmentWe use poetry to manage this project

1. Clone this repository
2. Run poetry install3. Activate the virtualenvironment with poetry shell(you can also use poetry run $command) Releasing a new version to pypi1. Edit pyproject.toml to update the version number
2. Commit the version number bump
3. Run poetry publish --build4. Push to GitHub
5. Create a new release in GitHub Possible improvements* Instead of checking one digit at a time, we could use a binary search-like algorithm. Eg. the following condition is equivalent to s3:ResourceAccount < 500000000000"Condition": {
"StringLike": {"s3:ResourceAccount": [
"0*", "1*", "2*", "3*", "4*",
]},
},* Similarly, there is a speed improvement possible by checking multiple digits per position in parallel (There is a small risk of being rate limited by STS when using this approach)

In practice this tool should be fast enough in most cases. Download S3-Account-Search

Deep Web
UPDATE: Jailbroken iphone hacked through ups phishing link

It's been about 2 weeks since and honestly nothing that out the ordinarys happened. My phone still acts weird. me not being able to lock it, use safari, view my files, see my recent calls. no death threats, blackmail attempts, kidnapping attempts yet lol. I keep getting dms from people on here telling me I should run for my life. Ngl still paranoid af.

submitted by /u/idefkaman
[link] [comments]

Pods Finance Bug Fix Postmortem
https://immunefi.medium.com/pods-finance-bug-fix-postmortem-61a576897ebd?source=rss------bug_bounty-5

SummaryContinue reading on Medium » (https://immunefi.medium.com/pods-finance-bug-fix-postmortem-61a576897ebd?source=rss------bug_bounty-5)

Hacking on Medium
Hacked: A Brief Migraine

Whoop-dee-fucking-doo

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video