To view the list of links, please access this site using Tor Browser.
If you’re seeing this message, access is restricted for regular browsers.
Already using Tor? If you are sure you’re currently in Tor Browser, proceed to our .onion version:
/u/notrustbutverify 📢 🍼 2 points
18 minutes ago
And since people are covering their lack of knowledge here's the treat by saying "it's a
wasn't + isn't
Enzyme here
SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u6 server_host_key: fingerprint:4c4M02lROUz1q9YPBG5mzDnaJ07db/E7XPmvFKzl4H8 fingerprint_sha256:e1ce0cd36951394cf5abd60f046e66cc39da274edd6ff13b5cf9af14ace5e07f 213.171.XX.XX:3128 3128 TCP/HTTP HTTP/1.1 501 method 'GET' not available Connection: close Cache-Control: max-age=0 Date: Mon, 23 Jun 2025 14:38:04 GMT Expires: Mon, 23 Jun 2025 14:38:04 GMT Pragma: no-cache Server: pve-api-daemon/3.0 213.171.XX.XX:111 111 TCP/PORTMAP program version netid address service owner 100000 4 tcp6 ::.0.111 portmapper superuser 100000 3 tcp6 ::.0.111 portmapper superuser 100000 4 udp6 ::.0.111 portmapper superuser 100000 3 udp6 ::.0.111 portmapper superuser 100000 4 tcp 0.0.0.0.0.111 portmapper superuser 100000 3 tcp 0.0.0.0.0.111 portmapper superuser 100000 2 tcp 0.0.0.0.0.111 portmapper superuser 100000 4 udp 0.0.0.0.0.111 portmapper superuser 100000 3 udp 0.0.0.0.0.111 portmapper superuser 100000 2 udp 0.0.0.0.0.111 portmapper superuser 100000 4 local /run/rpcbind.sock portmapper superuser 100000 3 local /run/rpcbind.sock portmapper superuser 213.171.XX.XX:123 123 UDP/NTP Version: 4 Close stratum: 3 Polling Interval: 4 Root Delay: 0.004791259765625 Root Dispersion: 0.0338897705078125 Reference ID: 1566532173 Reference Timestamp: 16992965818733728323
Let me first start off by saying that IP leaks do happen occasionally and they are stupidly easy to detect. However proving that it is the market's IP address's backend is a completely different situation. Phishing proxies will relay EXACTLY everything in the request. It is a MITM attack of course where the phishing proxy just overwrites the URL itself. Just because you search up some headers and see it is in the exact way doesn't mean it's from a the main fucking backend. The amount of times I have had to say this over and over and over again. They proxy everything, that is the fucking point. So of course it's going to look like a certain way.
In my view, from what I see here, this is almost 100% a phishing MITM proxy. How do I know? Because I have seen a similar one with the same proxmox situation just a couple weeks ago. If you think you got an IP leak and you fear that the admins won't pay a bug bounty (or will hide it) provide the information to dread staff and we can provide verification so it if falls through we post a message saying we have verified that is it correct.
There are many ways we can double check these things. Generally we just do a request flood maxing out their server's connection lines and see if the backend of the site goes down at the same time. There is also a request structure we can use to uncover if it is a phishing proxy. It's just stupid to assume this is the site's backend when the headers are the same. Like of course they would be. That is the fucking point.
I'll leave this up for 1 hour so people can see this comment and then remove this post.
We have no issue leaving it up, as i replied below, It's not ours so anyone who has it. Good luck with it!
-> /d/BlackOps/wiki?id=860b2749
And you post it on Pitch with your Enzyme account. What a fucking surprise.
You fucked up here, not us.
When there is an issue at hand you check, pay and solve it. Done. No ghosting whatsoever. Now you pay the price with /u/paris hidding your mistake. Typical from a /u/DeSnake shill right paris?
I won't be wasting my time in this post anymore.
Good luck.
We will talk at the booth.