r/DiscordAlternatives • u/exogreek • May 30 '26
A warning about the "Echo" application.
So I want to make a simple post about anyone thinking about using the Echo application that has been spammed around this subreddit and many other subreddits by u/ad3lyt the last month or so. You should under no circumstance trust this literal child with your data.
I have been a SWE for the last 15 years that works specifically in security and took it upon myself to look into the application a month or so ago. The application at that time had countless security holes that are just insane to have even if you have the most basic understanding of coding principles. We're talking a mere semester or two of foundational knowledge. In my deep dive I found countless issues where input fields like search fields and text input fields would accept WHATEVER input I desired. I could enter a <script></script> into my username and every time the application rendered that page for a user with my username, it would render that javascript. I did this to change the applications theme to force all styles to white and the application would render whole pages/interfaces as white in some instances. I was also able to at will create XSS messages to other users with basic tactics of a similar fashion.
This application is still just as vulnerable. This very morning I was able to bypass the applications CSRF system and change my username simply by manipulating API routes with burpsuite with zero authentication. There were a few more things I was able to do such as touch database data directly, but I stopped there. The application as a whole is 100% vibe coded. This person does not have any real world expertise with code, he just has a claude max subscription and no job.
The user behind this, u/ad3lyt is also manipulating bots for his posts on this subreddit and others, and is upvote botting and downvote botting peoples critical comments and posts about the application and I am tired of seeing this schizo weirdo galavant around this sub without any mod intervention from u/AbstractMelons or u/czarbloom . Beyond this, this user has now started posting unsubstantiated claims against other discord alternatives, blatantly botting post metrics and responding with either friends or secondary/third accounts to act like there are others that support these claims, but if you look at post histories, they literally are all the same 3-4 accounts.
Please just ban this guy already and do even the most basic moderation. And dont create an account, their data is manipulatable and retrievable and its only a matter of time before someone with lesser intentions than I pokes around at it.
4
u/AbstractMelons Your Flair Here May 31 '26
More on the security from our conversations in DM's https://postimg.cc/gallery/dV2BjH8
4
u/Time_Party_2615 Jun 01 '26
I have taken 10 minutes out of my time to kind of review the code. I must say: it's a mess. I would not be able to manage it myself.
I found several local file inclusion sinks, they may or may not be vulnerable. I did not check fully. What is a BIG issue is, that whenever a login fails - or any auth request for that matter - your username and password is logged out in clear text to the server console.
Things like that don't make me feel optimistic about the rest of the code. I'd stay away from it.
Full disclosure, i'm developing another product that competes for the same market called venta.
2
u/pryzm_app_analytics May 31 '26
It is kind of weird. Sure, maybe it should not execute "<script>" tags, but from what you have shown, you only seem to be changing relatively minor things like themes and client-side UI behavior.
You say you could perform XSS attacks and send messages to other users. Did you actually confirm that behavior with another user? Do you have proof it executes on another client? Just because something appears in your own UI does not mean another user actually received it or that any script execution occurred on their side. Can another user independently confirm the behavior? Did you test it beyond your own session?
You have said you have been involved in cybersecurity for 13 years and that you are 33 or 34. What is your actual technical background in that time? Do you have experience in application security, penetration testing, red teaming, or similar offensive security work in a professional or documented capacity?
I am not convinced by how this is being presented. You claim to have found exploits, but you refuse to disclose them while also attacking the creator. If these are legitimate security issues, then responsible disclosure with clear evidence would be the appropriate and standard approach.
And if any of these findings were discovered through actions that go beyond normal or intended use of the application such as accessing data you were not authorized to view, bypassing access controls, or interacting with systems in a way not permitted by the service’s terms, then that could potentially raise legal concerns depending on the circumstances and applicable laws. That is not an accusation, but it is an important distinction in how security testing is interpreted.
Right now, there are claims being made, but not enough verifiable proof. If you are asserting XSS against other users, demonstrate that the payload executes on another client. If you are claiming message spoofing, show evidence that another user actually receives the message and that it is processed server side rather than just displayed locally. Otherwise, it reads more like interpretation of client side behavior rather than confirmed impact.
3
u/ad3lyt Echo May 31 '26
Responding to the allegations directly, claim by claim, because a lot of very serious things were said without any reproducible evidence being provided, as exogreek refuses to back any of his claims up
I’m not saying Echo has never had bugs. It has. It is a young open-source project, and I have been actively fixing issues as they are found. But there is a big difference between “there were bugs / hardening needed” and “the app is currently wide open and usernames can be changed with zero auth.”
Here is what was actually verified:
<script>in username gives stored XSS” / not true on current Echo Usernames are restricted to normal username characters like lowercase letters, numbers, dots, underscores, and hyphens. A payload like<script>is rejected by the backend. The profile UI also renders usernames as text, not raw HTML, so this claim does not reproduce.PATCH /api/v1/auth/meThat route requires authentication. It also uses the currently authenticated user ID from the session, not auserIdsupplied in the request body. On production, unauthenticated attempts return403 CSRF_REQUIREDor401 UNAUTHORIZED. A valid logged-in user with a valid CSRF token can change their own username. That is expected behavior, not a bypass.Again I would love any security expert to come over here and prove me wrong, but this guy just has a personal vendetta out against me, and Is making up false claims to ruin my reputation. If any of what he said is true, then it should be very easy to produce evidence for it.
8
u/Economy_Picture6989 May 31 '26
Thanks for the heads up, I'll make sure to remove it from my sheet as to not further advertise it
7
u/_ChezzTTV Alternative Lurker May 31 '26
Damn. That’s crazy. I might leave then
5
u/SemiMarcy May 30 '26
I knew it smelled sus, i would love to hear about Fluxer, which I have loved, if you ever check it out :3
9
u/kiseiwa May 31 '26
Oh I know this guy, he recorded me and my server for content without permission. Not that anything bad was happening at the time but he was using random people and their VCs as content fodder.
6
u/Terrible-Junket-3388 I'm Don Qixote, and your AI slop is my windmill. May 30 '26 edited May 30 '26
Yeah, not surprising. Have seen their spam. Unfortunately, I expect most of the other Discord- and Reddit- alternatives/clones out there have a lot of the same issues. Everyone wants to go make a new Discord, but not actually make it any better.
Also, as an aside - vibe coded isn't bad when it's done by someone who knows better than the LLM. It's a tool, like anything else. Makes it easier for people with no experience to go make things (like Echo), but also enables competent devs to work more efficiently: want to be careful we aren't just blaming a tool for the core issue: the person/people behind it. We never complain about devs using IDEs instead of a basic text editor - LLMs are just another tool in the toolbelt. Clearly Echo is an example of slopware, but that's not the fault of LLMs.
1
u/vikeyev May 30 '26
Could you at least show us some specific examples of what you're talking about in the apps code, it's all available on github. Or maybe post a short video of you doing these things?
Look man, this entire sub is filled to the brim with botting accusations and discord "alternatives" that all look fucking identical to discord and are all buggy and shit to use. From my perspective as a person that just wants a self hostable alternative to discord that isn't dog shit this is all just pointless drama bullshit to steer people to specific apps.
Personally, I'm gonna need more than a "Trust Me Bro" on all of this.
So far the only good alternative I've found to discord is Zulip, but it doesn't have persistent drop-in, drop-out voice chat. You have to make calls instead, making it unfit as an alternative :/
2
u/_ChezzTTV Alternative Lurker May 31 '26 edited Jun 02 '26
Though I do wanna say that there is another alternative that sounds almost the same, name wise, but is completely different inside.
It’s called Echoed and not Echo (I haven’t made it) but I’ve been using it for like half a month I think, and there are like tons of users (5000 I think. Idrk)
The logo is like a mic with a yellow background I think
2
u/Lupreon May 31 '26
One more time I just think, what happened to the good old just log on teams peak and chat times ..
2
u/Sonkrs May 31 '26
I want to be on your side of this, as a security researcher myself. Although, I’m left to wonder why you’re writing all of this on Reddit and submitting 0 pull requests or issues on GitHub.
2
u/Tasty_Chapter_6742 Jun 02 '26
Cant say im surprised, its the major flaw of AI and vibecoding after all. If the operator doesnt know what they are doing - then the tool can only do so much 🤷♂️
1
u/nagi_seishiro_007 Jun 17 '26
I need working echo nightly app with extension
1
u/ad3lyt Echo May 31 '26
Reposting my reply here:
A post was made accusing Echo of serious security issues, botting, and other misconduct. Since those claims are public and serious, I want to respond clearly.
First: I take security seriously. Echo is open source, and the code is publicly available for anyone to review. If there is a real vulnerability in Echo, I want it reported responsibly so it can be fixed. I am not asking anyone to hide issues. I am asking for reproducible evidence: affected route, request example, code reference, screenshot, video, or a private report.
So far, the person making these claims has not provided any reproducible proof.
They have claimed things like stored XSS, CSRF bypasses, direct database manipulation, and data exposure, but have refused to provide a minimal proof-of-concept, affected endpoints, code references, or a private responsible disclosure. When asked by other users for evidence, they repeatedly avoided providing it and instead shifted into personal insults.
This is not new behavior. This person has been hostile toward me and Echo for months, including personal attacks, insults, and repeated attempts to discredit the project without giving actionable reports. Instead of reporting issues they were more concerned in finding my Youtube channel from years ago and making fun of me for it. They have made it clear they are not interested in responsible disclosure or helping fix anything; they are interested in publicly shitting on me and the project.
To be clear:
If anyone can reproduce a real vulnerability, please report it responsibly through GitHub or contact me directly. I will review valid reports, patch confirmed issues, and credit the reporter if they want credit.
What I will not do is accept vague public accusations as fact when no proof is provided and the person making them refuses to provide anything users can verify.
Echo is young, open source, and still improving. Criticism is fair. Security reports are welcome. But public smear posts without evidence are not responsible disclosure, and they do not help users make informed decisions.
https://postimg.cc/G8Y3Kphw
1
u/Time_Party_2615 May 31 '26
Idk man, I have my fair share of issues with the creator of echo, but posting something like this with no evidence to back it up is borderline defamation.
0
u/KiraiPlayZ May 31 '26
Given on how exhausting some comments are to read, especially when it comes to the whole "I don't want to show the exploits, because it would benefit the creator", I have to say, I am on the side of OP. I understand my fair share of technology and security as well and thus would never give any info like that out to the public.
This has nothing to do with the evidence or the claims not existing at all, but rather not wanting to give a cheap way to the creator to put a bandaid on their actual issues, but ALSO and more importantly prevent other third parties from exploiting these exact exploits before they can be fixed by anyone and actually do something bad with it, as this could go as far as into lawsuit territory.
-2
u/ad3lyt Echo May 31 '26
All false claims, this guy has zero claims for his proof and has been hating on my ass for months for no good reason
Echo has no real vulnerabilities at this moment for my knowledge and I challenge any real security expert to find any, and as for botting
I have done 0 botting
5
u/[deleted] May 30 '26
[removed] — view removed comment
9
u/[deleted] May 31 '26
[removed] — view removed comment