📢 Update on @PlayeonBot

We have finally received an official response from Telegram after 9 days of waiting

Combined with our internal system audit, we have identified the exact reason why the bot was banned

It turns out this was not a random platform issue or a bug on Telegram’s side, but the result of an external security breach and deliberate sabotage

We are currently finalizing the verified timeline and evidence and will be publishing a detailed case study tomorrow

Thank you, everyone, for your patience, understanding, and continued support

🛡 Case Study & Security Breach Report

Following our internal audit, we have confirmed 100% certainty regarding the actor behind the deliberate sabotage of @PlayeonBot and @FluxifyBot.

The breach was carried out by @ItzRahul, affiliated with the @NexGenBots network, operating from IP 49.36.26.2 (Bhopal, MP).

The complete forensic logs, timeline correlation, and full technical proofs are documented in the attached file incident_report.md.

We strongly advise the community to avoid sharing infrastructure or dealing with @ItzRahul and @NexGenBots.

Playeon Early Source Release

Due to our private source code being compromised by an unauthorized party, we are preemptively publishing Playeon's source code on GitHub to establish official authorship:

Repo: https://github.com/playeon/playeon

Note: The project is incomplete and in active development, so expect bugs and unfinished features

We may not push any updates to this repository in the future, as we’ll be working on a fresh new codebase for Playeon

ℹ️ All the codebase comments and README.md documentation were generated by Gemini AI

📢 We're creating a new replacement bot that will remain active until the original Playeon bot is recovered

💬 You can now use @AudiumBot as the new Playeon/Fluxify bot

We’ll be continuing development on this bot and bringing new features to it from now on

For now, all Playeon/Fluxify users can switch to @AudiumBot

📢 Incident Resolution & De-escalation

Following our recent announcements and legal actions, Rahul (@ItzRahul) reached out directly to me to take responsibility for his actions

He has now issued an official public apology on his channel:
https://t.me/NexGenBots/405

In his statement, he acknowledges the interference with Playeon bots, admits full responsibility for disrupting our work, and commits to not repeating this behavior

Our primary goal has always been protecting our project and holding bad actors accountable

Since he has stepped forward, admitted his wrongdoing publicly, and agreed to cease all interference, we have agreed to de-escalate and halt further legal escalations regarding this matter

Thank you to our community for the support throughout this incident

Playeon is moving forward, focused entirely on building and serving our users

@xysushi
Lead Developer, Playeon

📢 Important Update

@AudiumBot is currently down due to a server outage

You'll need to wait until we arrange a new server to get Audium back online