BlockBeats Statement on Erroneous Reporting Regarding the fomo App

At 19:38 on September 23, 2026, BlockBeats published and pushed the news article "Fomo Official iOS App Contains Crypto-Stealing Malware."

In fact, the app's full name is "FomoPeek," and our push method led many users to misunderstand that users of the currently very popular trading app fomo App were at risk of having their assets stolen.

Soon, our content error sparked widespread discussion on social media, with many questioning whether the message was a "paid placement (hit piece)" from a competitor

Because during the same period, overseas KOLs began collectively criticizing losses from trading on fomo, saying that fomo's leaders were collectively pumping tokens to deceive retail investors.

After learning of this situation, our team immediately launched an internal review. First, we confirmed that none of BlockBeats' business cooperation activities have ever included so-called paid smear campaigns between competitors. Even if we had received similar requests in the past, we would directly refuse them. So we focused on whether any content colleagues had privately accepted a "paid hit piece."

We reviewed the entire publishing process of that content. In fact, as early as September 19, we had published the news about security risks in "FomoPeek" at the first opportunity. But the product was not well known, so it did not trigger any industry discussion.

For security-related news involving user assets, our consistent requirement is that the sooner everyone knows, the better. On the one hand, this is what users truly need to know; on the other hand, such news indeed attracts relatively high attention, so the traffic is also relatively good for us. Therefore, regardless of whether the security incident is big or small, we will report it at the first opportunity.

So on the 23rd, when another source also published this security news, our editor on duty again chose to publish it at the first opportunity. But unexpectedly, what that source reported was the security risk warning about "FomoPeek" that we had already published a week earlier.

Our editor on duty did not confirm and verify the name again, and directly wrote "fomo" when publishing. The most basic error caused the most serious consequences.

fomo App is already a name known to almost everyone in the industry, yet we wrote it together with a piece of malware. Here, on behalf of all colleagues at BlockBeats, I sincerely apologize to the fomo team and to everyone affected by this erroneous information.

At the same time, we can confirm that there was no "paid smear article" behavior at any point in the process.

Regarding this news editor, we have already taken action. We quickly verified the entire process and confirmed where the responsibility lies. We will also treat this news item as a case internally and re-emphasize our review process once again.

After discovering the problem, we immediately took down that news article. We began remedial measures at the first opportunity. Users could no longer see this news on the homepage, in search, or across our various distribution channels. We then updated the latest, correct version, correcting the name of the malware to FomoPeek, and all subsequent distribution was based on the corrected version. To users who have already seen the incorrect version, we apologize again here. We cannot completely erase this impact, but going forward, we will make up for it with stricter standards for every piece of content.

In the years since BlockBeats entered the industry, it has remained focused on doing just one thing: content. Especially in a market environment like the past two years, when there is little innovation in the industry, highlights deserve even more care. This is our original intention as a media outlet and the reason we are willing to keep doing this.

After the incident, we saw many users reach out to us or @ us through various channels and platforms to tell us the news was wrong. We were truly moved and also deeply ashamed that we let everyone down.

From now on, for any content involving security, specific entities, and product names, we require a second verification before publication. If you find any errors in our content in the future, please also tell us directly just as you did this time. This is a tremendous help to us.

We hope this apology letter can earn the understanding of our readers and users, Fomo users, and all community users.

Once again, we sincerely apologize.

Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia