Suspicious "Private Document" verification page.
The page asks visitors for their email address, then uses JavaScript obfuscation (Base64 + string reversal) to redirect victims to an external domain while appending the supplied email address to the URL.
URLs:
hxxps://www.test[.]engelconsulting[.]ci/secure_integration.html
hxxps://0xdff5bcee57809c2062cd5b38febee9ae61b47e5erh4[.]com/?ymnecxtp
#phishing@500mk500
Document Download phishing lure impersonating a secure file-sharing portal.
The page displays a fake "Encrypted End-to-End Document" message and redirects users to a second-stage site when the "View / Download Document" button is clicked.
URLs:
123plochki[.]online
securedoc.labsuface[.]com
#Phishing#CredentialHarvesting@500mk500
Suspicious "Google Meet audio issue" page
The site impersonates Google/Gemini, tracks visitors, polls a backend for instructions.
URL: audio92872[.]icu
#Phishing@500mk500#Google
One row per rule. Every command line, host, user collapsed into one pivot.
That's what VALUES() does in ES|QL. It collects all distinct values of a field inside each group, so they survive the aggregation.
Without VALUES(), STATS gives you a count.
With it, you get every command, every path, every host that fired under that rule. All on one row.
150+ alerts become 15 rules.
Stop reading alerts. Start reading rules.
ssh.exe -R proves a tunnel exists. It doesn't prove a pivot.
Identical flag in all three rows. What separates a benign port-forward from a SOCKS subnet sweep is the shape of the traffic: fan-out and failure count, not the command line.
Full breakdown drops Thursday.
KQL + ES|QL so you hunt it the same day. 🔍
I gained access to the threat actor’s server due to their bad SECOPS. Later, they discovered and removed my backdoor and patched the vulnerabilities I used.