CryptoSlate reported on 2026-09-10 that a crypto project paying nearly 1 million people a daily income had its reserves looted. The claim remains unconfirmed and carried a desk confidence of 18 out of 100.
The same publisher stated that a malicious Super App bypassed stream liquidations prior to a Sept. 4 hotfix. The hotfix restored whitelisting and closed detected insolvent accounts, according to CryptoSlate.
Reported reserve looting at payout project
CryptoSlate reported on 2026-09-10 that a crypto project had its reserves looted. The project reportedly paid nearly 1 million people a daily income. The claim appeared in a post on the publisher's site.
The publisher did not name the project in the headline. No asset was recorded in the supplied story facts. The report remains officially unconfirmed as of the provided data.
Malicious Super App bypass
A malicious Super App bypassed stream liquidations, according to CryptoSlate. The bypass took place before a hotfix dated Sept. 4. The publisher described the application as malicious in its desk summary.
No relationship between the app and the project was recorded in the facts. The story listed no company or protocol involved. The claim stands as a separate reported event.
Sept. 4 hotfix measures
The Sept. 4 hotfix restored whitelisting, CryptoSlate stated. It also closed detected insolvent accounts. The corrective action followed the reported bypass of liquidations.
The hotfix preceded the Sept. 10 publication by six days. The publisher flagged the sequence in its summary. No further technical detail was provided about the fix.
Whitelisting restoration detail
Whitelisting was restored on Sept. 4 per the report. The measure limited access after the detected bypass. The publisher did not specify the exact mechanism used.
The restoration accompanied the closure of insolvent accounts. Both steps formed part of the same hotfix. The report gave no update after that date.
Insolvent account closures
Detected insolvent accounts were closed by the hotfix. The closure addressed the insolvency that was detected. CryptoSlate reported the action without naming any entity.
No count of closed accounts was supplied. The facts recorded no organizations involved in the process. The closure stood as described in the summary.
Publisher and attribution
The post appeared first on CryptoSlate, the desk summary noted. The timeline anchored the report to 2026-09-10 at 17:50 UTC. The publisher carried the story as market news.
No other source was attached to the provided facts. The report carried a single publisher attribution. The desk treated the item as unconfirmed.
Absence of named entities
The provided facts listed no assets, companies, or people. Organizations and protocols were none recorded. Blockchains and countries were also absent from the data.
The absence limits independent verification of the claims. The report did not fill those identification gaps. Readers see only the publisher's statements.
Desk confidence and confirmation
The provided desk confidence scored 18 out of 100. The low score reflects the unconfirmed status. Officially confirmed was marked no in the facts.
The market impact read was bearish per the desk. The event type was tagged as flows. These labels came from the supplied summary.
Market and flow classification
The story type was market or markets in the facts. Event types included flows as noted. No price data accompanied the report from the publisher.
The bearish read suggests a negative desk tone. No numerical impact was stated for the market. The classification stands as provided.
Report timing and sequence
CryptoSlate published the looting claim on 2026-09-10. The hotfix date of Sept. 4 came earlier in the sequence. The facts bind the timeline as given without further dates.
The publisher's summary combined both claims. The combination appeared in one desk entry. No additional timeline entries were recorded.
Daily income payout claim
The project reportedly paid nearly 1 million people a daily income. The figure of nearly 1 million comes from the publisher's headline. No breakdown by region was provided.
The payout detail underscores the scale of the reported project. The reserve looting may affect that payout, but the facts do not state this. The claim is attributed to CryptoSlate.
Stream liquidation function
Stream liquidations were bypassed by the malicious Super App. The term stream liquidations appeared in the desk summary. No definition was given in the facts.
The bypass occurred before the September hotfix. The publisher did not name the platform running the streams. The event was reported as a discrete action.
Detected insolvency note
Detected insolvent accounts were referenced in the hotfix description. The insolvency was detected prior to closure. No measurement of insolvency was recorded.
The closure formed part of the Sept. 4 action. The publisher did not link the insolvency to the reserve looting. The facts keep the two claims separate.
Reader information
The report remains unverified by official sources. The desk confidence is low at 18 out of 100. No investment advice follows from this copy.
The article uses only the supplied facts. No external context was added to the prose. The writing follows wire discipline throughout.
Market context
The desk assigned a bearish market impact read to the story. The event was classified under flows. No price data was supplied with the report. Market structure details beyond the bearish label were not included in the source.
What it means for the industry
The reported events indicate a security bypass and a subsequent corrective hotfix, according to CryptoSlate. The desk classified the market impact as bearish and the event as flows. No broader sector change was explicitly stated in the facts.
Key takeaways
- CryptoSlate reported on 2026-09-10 that a crypto project paying nearly 1 million people a daily income had its reserves looted.
- The same publisher stated a malicious Super App bypassed stream liquidations before a Sept. 4 hotfix.
- The hotfix restored whitelisting and closed detected insolvent accounts, according to CryptoSlate.
- The report recorded no assets, companies, or individuals involved in the incident.
- The desk assigned a bearish market impact read and tagged the event as flows.
The report remains unconfirmed as of the provided facts. The desk confidence stands at 18 out of 100. Observers should monitor further publisher updates for verification.
Newsroom intelligence
The short version
CryptoSlate reported on Sept. 10 that a crypto project paying nearly 1 million people a daily income had its reserves looted. The publisher also described a malicious Super App bypassing stream liquidations before a Sept. 4 hotfix that restored whitelisting and closed detected insolvent accounts.
AI-assisted summary · reviewed against the cited reporting
How this story developed
- createdCryptoSlate
A crypto project paying nearly 1 million people a daily income just had its reserves looted
A malicious Super App bypassed stream liquidations before a Sept. 4 hotfix restored whitelisting and closed detected insolvent accounts. The post A crypto project paying nearly 1 million people a daily income just had its reserves looted appeared first on CryptoSlate .
Sources & verification
- 1.CryptoSlate reported on 2026-09-10 that a crypto project paying nearly 1 million people a daily income had its reserves looted.CryptoSlate · published
- 2.## Reported reserve looting at payout project CryptoSlate reported on 2026-09-10 that a crypto project had its reserves looted.CryptoSlate · published
- 3.The project reportedly paid nearly 1 million people a daily income.CryptoSlate · published
- 4.4 hotfix restored whitelisting, CryptoSlate stated.CryptoSlate · published
- 5.CryptoSlate reported the action without naming any entity.CryptoSlate · published
- 6.## Report timing and sequence CryptoSlate published the looting claim on 2026-09-10.CryptoSlate · published
- 7.## Daily income payout claim The project reportedly paid nearly 1 million people a daily income.CryptoSlate · published
- 8.The figure of nearly 1 million comes from the publisher's headline.CryptoSlate · published
Last verified · Not financial advice. See our editorial policy and risk disclosure.
Questions readers are asking
- What did CryptoSlate report on Sept. 10?
- CryptoSlate reported that a crypto project paying nearly 1 million people a daily income had its reserves looted. The publisher also described a malicious Super App bypassing stream liquidations before a Sept. 4 hotfix.
- What action did the Sept. 4 hotfix take?
- According to CryptoSlate, the Sept. 4 hotfix restored whitelisting and closed detected insolvent accounts. The fix followed a reported bypass of stream liquidations by a malicious Super App.
- Was the report confirmed?
- The story is officially unconfirmed according to the provided facts. The desk confidence score was 18 out of 100. No assets or companies were named in the report.
- What market impact was assigned?
- The desk assigned a bearish market impact read to the story. The event was tagged as flows. No price data accompanied the report from CryptoSlate.
Story record
- Published
- Reading time
- 4 min
- Beat
- Markets
- Story status
- developing
- Sourcing
- 1 publishers · 1 domains
- Editorial score
- 58 / 100
- Quality score
- 83 / 100
Sign in and reach the end of the story to qualify. Rewards are awarded server-side after read verification. Rewards Rules.
Signal beyond the noise, once a day
One email with the stories that moved markets, what changed since yesterday, and what our newsroom is watching next.
The Crypto News Hub News Desk is our organizational newsroom byline for reports produced from verified public sources using the publication's automated research and quality controls. Reports flagged by those controls — for accuracy, sourcing, high risk or duplication — are held and reviewed by our human editors before publication. This byline does not imply that every piece was individually rewritten or signed off by a named journalist.
Reader feedback
We correct in the open. If something here is wrong, incomplete, or missing context, tell us and we will publish the correction with a version note.
