🍺 Taberna do Eric Ϟ

to everyone who witnessed this, I just have one thing to say:

kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk

On Monday, the work will begin.

🔗 List of projects that will be published in this group
(all links are public project sources)

✅ Confirmed:

— YouTube Morphe (patched by me): https://github.com/MorpheApp/morphe-patches/releases/tag/v1.42.0

— MicroG RE (only new updates): https://github.com/MorpheApp/MicroG-RE/releases/tag/7.1.1

— Metrofuse (only updates): https://github.com/956tris/MetroFuse/releases/tag/7.2

⌛ In progress:

— PlayintegrityFix NEXT: https://github.com/EricInacio01/PlayIntegrityFix-NEXT

NOTE: This list will be updated periodically, with new projects being added and others being removed.

They told me that I am the messenger of chaos, and that I only bring bad news. Is that true?

🚨 PlayIntegrityFix, TrickyStore & Yuri Keybox Are at Risk. Starting February 2026, the current keybox workaround used with tools like Yuri Keybox, PIF, and TrickyStore may no longer work. Google is rolling out mandatory Remote Key Provisioning (RKP) with…

that is why pif-next will return.

there will be no miracles, and the community needs to know that.

you don't need to sell something to prove it works; that's how a community is built.

while some make distinctions, I bring news and always inform. ALWAYS.

Unfortunately, my uncle passed away before he could witness the release of GTA VI. It really affected me, because he was the one who introduced me to GTA V when it was released in 2013. It was also the first time I ever played on a console, an Xbox.

He even watched the trailer that was released in 2025 and told me how excited he was for the game to come out this year. Sadly, just one month after the trailer was released in 2025, he passed away...

Did you miss me?

And yes, that’s true. The developer themselves has confirmed that it does indeed collect your phone number.

Which is regrettable, as there is no prior warning and data is collected without the user’s consent.

Switch your Telegram client.

https://t.me/NekoChat/620439

How does it work technically?

The backdoor is hidden inside the Extra.java file, which appears as a harmless placeholder in the public GitHub source code. In the officially compiled and distributed APK, this file contains extra code injected manually during the build process — meaning the malicious code is not visible in the public repository.
When triggered, the code does the following:

1. Iterates through all 8 account slots available in the Telegram client
2. Extracts the phone number and User ID of each logged-in account
3. Builds a JSON map in the format {"ID": "+1number", ...}
Silently sends everything via Inline Query to the bot @nekonotificationbot.

The use of Inline Query is intentional: this method does not appear in the user's chat history, requires no prior interaction with any bot, and generates no visible notification. It is silent by design.

All critical strings in the code (bot name, secret key, etc.) are obfuscated using custom encryption algorithms to hinder detection.

What did the developer say?
The developer claimed the bot is used solely to "parse usernames." However, the decompiled code clearly shows extraction of the phone field — not just usernames. The explanation does not match what the code actually does.

The GitHub issue (#336) was locked by the Nekogram developers shortly after it was opened.

Proof & Sources:

🔗 Full technical analysis: https://thebadinteger.github.io/nekogram-phone-exfiltration/
🔗 GitHub issue (locked): https://github.com/Nekogram/Nekogram/issues/336
🔗 Video proof: https://t.me/romashka_gene/8
🔗 Proof-of-concept repo: https://github.com/RomashkaTea/nekogram-proof-of-logging

📣 NEW PIF-Next version!

Due to Google’s new strict rules, please watch the tutorial and follow the installation instructions: Click here.

Changelog:
* STRONG_INTEGRITY universal — working on your uncle’s Redmi Note 5
* HyperStealth™ — undetectable even by the NSA
* Widevine L1 on a 720p screen via “quantum spoofing”
* Google Pay by sheer willpower
* RKP hacked without Google knowing
* Auto-update via time travel
* Fix for the "pif.json infinite loop"
* YouTube Premium for free "by accident"
* Experimental support for iOS 18 ("we're not sure how we got here")
* Motivational message on boot

A new update is scheduled to be released on this date.

However, I'm not going to tell you now, but in the next few days you're going to like it a lot :)