Original title: Rhythm BlockBeats’ statement regarding its incorrect report about the fomo App
Original author: Rhythm BlockBeats
Original source: https://www.theblockbeats.info/news/63796
Reposted by: Mars Finance
On September 23, 2026 at 19:38, Rhythm BlockBeats published and pushed news about (Fomo’s official iOS app includes a crypto-stealing malware).
In fact, the full name of the app is “FomoPeek”, and our way of posting led many users to misunderstand that users of the currently very popular trading app fomo App are at risk of having their assets stolen.
Soon, our content errors sparked widespread discussion on social media, and many people questioned whether the message had been affected by a competitor’s “paid promotion (black PR)”.
Because during the same period, overseas KOLs began to collectively denounce the losses incurred from trading on Fomo, saying that Fomo’s front-end team issued group calls to lure and scatter retail investors.
After learning about this situation, our team immediately carried out a self-audit. First, we found that none of Lyudong BlockBeats’ business collaboration activities have ever included so-called paid smear campaigns against competitors. Even if we had previously received similar requests, we would directly reject them. Therefore, we focused on whether any content staff member privately accepted “paid black copy.”
We reviewed the full publication process of this content. In fact, as early as September 19, we published the news about the safety risks of “FomoPeek” immediately. But since this product was not widely known, it did not spark any industry discussion.
For safety-related news, involving users’ assets, our consistent requirement is that the sooner everyone knows, the better. On the one hand, this is truly information users need to know. On the other hand, this kind of news has high attention, so for us, traffic is also relatively good. Therefore, whether the safety incident is big or small, we will report it immediately.
So on the 23rd, when other sources published this safety news, our on-duty editor still chose to publish it immediately. But we didn’t expect that what this source reported was the safety risk warning for “FomoPeek,” which we had already published a week earlier.
Our on-duty editor did not confirm and verify the name again, and instead published it directly as “fomo.” The most basic mistake has the most serious consequences.
The Fomo App is a name that nearly everyone in the industry knows. Yet we linked it to a piece of malware. Here, on behalf of all my colleagues at Lyudong BlockBeats, I sincerely apologize to the Fomo team and to everyone who was affected by this incorrect message.
At the same time, we can confirm that throughout the entire process, there was no “paid black copy” behavior.
Regarding this news editor, we have already handled the matter. We quickly verified the entire process and confirmed where responsibility lies. Internally, we will also treat this incident as a case and once again emphasize the review process.
After discovering the problem, we immediately took down that news item. We started remediation measures right away. Users could no longer see the news on the homepage, in search, or through our various distribution channels. Then we updated to the latest correct version, correcting the malware name to FomoPeek. All subsequent distribution will be based on the corrected version. For users who have already seen the incorrect version, I want to say sorry again here. We cannot completely erase the impact, but for every piece of content going forward, we will make up for it with even stricter standards.
Over the years that Lyudong BlockBeats has been in the industry, we have always focused on doing content. Especially in the past two years, in such a market environment, the industry has had few innovations, and we should protect the highlights even more. This is our original intention to be a media outlet, and it is also why we are willing to keep doing this.
After it happened, we saw that many users found us through various channels and platforms, or @ us, telling us that the news was wrong. We were genuinely moved and also very ashamed for letting everyone’s trust down.
In the future, for any content involving safety and specific entities and product names, we require a second verification before publishing. If anyone discovers that we have content errors, please tell us directly as you did this time—this is a great help to us.
This letter of apology hopes to win the understanding of our readers and users, Fomo users, and community members.
Once again, I offer a sincere apology.