NucleiFuzzer
A powerful automation tool for detecting xss,sqli,ssrf,open-redirect..etc vulnerabilities in web applications.
https://t.co/rP70E8X6Z1
#infosec#pentesting#bugbounty
🚨 A vulnerability in Telegram’s widget engine can lead to native code execution on affected clients
Research: https://t.co/sV01sQKweE
The issue stems from a QuickJS-ng parser bug that can trigger out-of-bounds memory corruption when a crafted Telegram widget is processed. According to the researcher, exploitation can occur during message rendering without requiring the user to open the widget.
Telegram Widgets | Remote Code Execution:
Impact: Native code execution
Android: RCE demonstrated on affected builds
iOS: RCE demonstrated on affected builds
Status: Later Telegram builds include mitigations
The research also documents additional memory corruption and use-after-free issues affecting Telegram’s widget engine and underlying QuickJS-ng implementation.
Per Telegram... "This issue in Telegram for Android was fixed yesterday, and the fix was deployed to all users earlier today."
During infrastructure hunting with @Huntio, I identified an exposed HTTP directory containing 1,785 files across 21 subdirectories (~780 MB in the captured snapshot).
The directory contained more than staged payloads.
I found PowerShell TCP beacons configured to connect on port 8443, paired with a Python listener. The beacon sends a BEACON|hostname|username|cwd banner, executes received commands using Invoke-Expression, and returns output between BEGIN and END markers.
Additional payload variants used Base64-encoded PowerShell and XOR-obfuscated content. One loader also attempted AMSI tampering through .NET reflection.
The Metabase scripts submitted native PostgreSQL queries through /api/dataset, attempting OS command execution via COPY ... FROM PROGRAM. Other scripts attempted payload deployment and trigger-based persistence.
The exposed workspace also contained Masscan results covering 40,922 open-port records across 21,745 unique IPs, along with Redis, Elasticsearch, MongoDB, MySQL, and SMTP enumeration tools.
SMTP credentials were stored in plaintext, alongside scripts attempting to transmit them to an external mailbox.
Most concerning were the NAS collection scripts and logs: 109 client directories were enumerated, with 16 archive operations reporting approximately 6.6 GB of collected data.
These findings document the tooling and recorded activity, not confirmed success across every stage. Live C2 sessions, successful Metabase exploitation, and the contents of the reported NAS archives remain unverified.
Sensitive credentials and potential victim data have been excluded from the screenshots.
Payment Bypass via an Exposed Test Endpoint
While testing a web application, I identified a payment bypass vulnerability caused by a test endpoint exposed in production.
#BugBounty#CyberSecurity#WebSecurity#PenetrationTesting
1/8
Find AD attack paths without BloodHound 👇
*nothing against bloodhound by the way. It’s awesome. There’s many ways to do this. I like to recommend this way for IT admins because I think it’s easier to get value quicker.
@cyberthreatpov
While hunting for suspicious infrastructure on @Huntio, I came across an exposed staging directory containing 57 artifacts, including 24 Python scripts, a Windows Chisel binary, operational logs, and Base64-encoded PHP tooling.
The Python scripts covered Oracle and SSRS authentication attempts, WinRM access checks, https://t.co/XaofqcRdrA probing, API enumeration, and credential attacks against multiple services. Several scripts were configured with specific targets and hardcoded credentials.
One of the more interesting findings was a pair of Base64-encoded PHP scripts designed to relay SOAP requests to an internal payment service.
After decoding them, I identified code that accepts parameters through HTTP requests, constructs SOAP envelopes, and forwards them using HTTP POST with SOAPAction headers.
Two operations stood out:
ConsultaSdo: Account balance inquiries
AplicaPago: Payment processing
A separate Chisel log recorded a reverse-tunneling listener starting on port 8443.
What made this directory interesting wasn't any single tool, but the combination of authentication attacks, internal service probing, tunneling infrastructure, and code targeting financial operations.
The artifacts provide evidence of attack preparation and attempted access, but don't establish a successful compromise or payment manipulation.
As if PHP2Shell wasn't enough for one day... now GitLab. 😅
🚨 CRITICAL GITLAB ALERT (CVSS 10.0)
CVE-2026-110264 could allow unauthenticated RCE on self-managed GitLab servers.
⚠️ Potentially affects 12 years of releases, dating back to 2014.
Patches available. Update immediately!
https://t.co/MtIwEFk7QY
#gitlab #cybersecurity