If you, like many, think relying just on `cat` command's output is enough to be sure about the integrity of a bash file. Think twice, you could get hacked. Read below 👇

RT @0xAsm0d3us: New writing/research ✒�� Fragility of The Internet: How Sacrificial Nameservers allowed potential DNS hijacking of 1.6+ mil…

@coffeebreak_YT Signs of low trust society

New writing/research ✒️ Fragility of The Internet: How Sacrificial Nameservers allowed potential DNS hijacking of 1.6+ million domains Article:

@DaneSherrets ChatGPT is fine, but others...

On Jul 25th 2016, tiktok[.]com (along with 1.3 million+ domain names) suddenly became susceptible to DNS hijacking. As you can see from the NS record history for tiktok[.]com A fun task for you. Can you figure out what was the root cause of this behavior?

Damn Vulnerable GraphQL Application is an intentionally vulnerable implementation of Facebook's GraphQL technology, to learn and practice GraphQL Security. #hacking #graphql #cybersecurity #bughunting

@Lyutoon_ Nice work!

@akita_zen @Blaklis_ AI created this garbage in the first place, ever since LLMs came into picture, no. of BS reports skyrocketed especially in Web3 programs. They make it seem like a Critical issue, when it is actually plain BS.

@ThisIsDK999 AI influencers

Scammers are actively exploiting numerous open redirects and using them to index 302 redirects on Google. They are taking advantage of this by indexing pages related to betting, casino, and gambling sites. Surprisingly, Google ends up indexing these 302 redirects. For example, if an open redirect is found on example[.]com, scammers can index example[.]com/redir?url= https://malicious[.]com, and Google will display the title of malicious[.]com under the URL of example[.]com. It’s a reminder that open redirects can be a serious issue that needs fixing. All the sophisticated security controls in the world won’t matter much if scammers can exploit something as simple as this.

@neembu_paani31 @himanshustwts Not to be salty, this is the most amount BS I read in a day.

Horrors of DNS: A Tale of 1800 potential domain takeovers due to mistyped NS I analyzed all the root domain names across 1000+ TLDs and discovered that there are around 1800+ domain names which are using mistyped NS (".ne" vs ".net"). This directly puts these domains at the risk of being hijacked. The study was inspired by a real-world incident involving MasterCard, where a typo in their DNS configuration could have been exploited by malicious actors. Read my full research here:

Original Trojan source paper:

A neat trick for bypassing WAF/filters while testing for OS command injection vulnerabilities. Use shell globbing / wildcard expansion. Here is an example `cat /e*c/p*s*d` is equivalent to `cat /etc/passwd`. But how? Before cat runs, the shell expands the glob pattern /e*c/p*s*d to match actual files and directories in the filesystem. `/e*c`: The shell interprets this as "any path starting with /e, followed by zero or more characters (*), ending with c." `/p*s*d`: This matches a path or file name starting with p, followed by zero or more characters (*), then s, then zero or more characters (*), then d #bugbountytips #hacking

@nav1n0x If the server is deemed to be vulnerable, but a WAF is present: `../../../../../../e*c/p*s*d{{`

At HackerOne, we have already been doing this for years. Many of our triagers have prior experience in bug hunting (some of them are top hackers in several programs) and with years of expertise in the field. In fact, prior bug hunting experience is a major plus for triage-related roles. While certifications are not mandatory, they are certainly a plus. If you're an accomplished bug hunter interested in triaging, head over to HackerOne Careers and apply!

Time of check to time of use (TOCTOU) Attacks in GitHub workflows: One of the lesser known evils, occurs when a malicious actor submits a seemingly harmless pull request, waits for approval, and then updates the pull request with malicious code before the workflow execution. Happens because the workflow uses a mutable reference (e.g., branch name) instead of an immutable one (e.g., commit SHA). Can occur with pull_request_target and issue_comment triggers. How to fix? Use an immutable reference (e.g., commit SHA) instead of a mutable one (e.g., branch name)

⚡ GitHub Actions Attack Vectors Gist: