BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile
BlockSec Phalcon

@phalcon_xyz

A Platform to Monitor and Block Hacks | The only one boasting dozens of successful white-hat rescues. | Built by @BlockSecTeam

👉TG: t.me/BlockSecTeam

ID: 1278266969532203008

linkhttps://blocksec.com/phalcon calendar_today01-07-2020 09:59:43

855 Tweet

5,5K Takipçi

39 Takip Edilen

BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

Indeed, the AToken price for USDT was incorrectly shown as $154 during the Astera.fi exploit. However, this was not a "textbook oracle misconfiguration". The root cause appears to be token price manipulation resulting from insufficient market liquidity. The AToken price =

Indeed, the AToken price for USDT was incorrectly shown as $154 during the <a href="/asterafinance/">Astera.fi</a> exploit. However, this was not a "textbook oracle misconfiguration". The root cause appears to be token price manipulation resulting from insufficient market liquidity.

The AToken price =
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

🚨 It’s live! Phalcon Compliance Self-Service Platform by BlockSec — your real-time AML solution for crypto compliance. ✅ 400M+ labeled addresses ⚡️ Millisecond-level response 🌍 FATF-aligned across 27+ jurisdictions 🔍 Seamless MetaSleuth integration BlockSec MetaSleuth Detect

BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

Our system detected several suspicious transactions (initiated by different EOAs) targeting two unknown contracts deployed by the same address on #Ethereum hours ago, resulting in losses of ~$120K. The root cause appears to be a lack of access control on the critical functions

Our system detected several suspicious transactions (initiated by different EOAs) targeting two unknown contracts deployed by the same address on #Ethereum hours ago, resulting in losses of ~$120K.

The root cause appears to be a lack of access control on the critical functions
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

.Sharwa.Finance was reported to be exploited and subsequently paused (as claimed by the project). However, several additional suspicious transactions occurred hours later, likely exploiting the same underlying issue through slightly varied attack paths. In general, the

.<a href="/SharwaFinance/">Sharwa.Finance</a> was reported to be exploited and subsequently paused (as claimed by the project). However, several additional suspicious transactions occurred hours later, likely exploiting the same underlying issue through slightly varied attack paths.   

In general, the
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

ALERT! Our system detected an attack transaction on #Base a few hours ago, targeting an unknown contract and resulting in a loss of approximately $219K (55 WETH). The root cause appears to be improper access control, which allowed arbitrary transferFrom calls. As a result, the

ALERT! Our system detected an attack transaction on #Base a few hours ago, targeting an unknown contract and resulting in a loss of approximately $219K (55 WETH). The root cause appears to be improper access control, which allowed arbitrary transferFrom calls. As a result, the
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

ALERT! Balancer and several forked projects have been attacked. Any forked projects should stay alert and monitor closely! The losses were as follows: Eth: balancer, 70m Base: balancer, 3.9m Polygon: balancer, 117k Sonic: beets, 3.4m Arb: balancer, 5.9m Op: beethoven, 283k

BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

Tough day. Balancer If you want an extra shield, we can help. Early-detect in mempool + auto blocking (pause / frontrun) — across ETH, Base, Arbitrum, Polygon, Sonic, OP. Our DMs are open—happy to set you up in minutes.

BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

.Balancer and several forked projects were attacked a few hours ago, resulting in losses exceeding $120M across multiple chains. This was a highly sophisticated exploit. Our initial analysis suggests the root cause was an invariant manipulation that distorted the BPT price

.<a href="/Balancer/">Balancer</a> and several forked projects were attacked a few hours ago, resulting in losses exceeding $120M across multiple chains. This was a highly sophisticated exploit. Our initial analysis suggests the root cause was an invariant manipulation that distorted the BPT price
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

ALERT! Our system detected a series of suspicious transactions targeting Moonwell’s smart contracts on #Base and #Optimism. Our analysis indicates an issue with the token price (rsETH / ETH) feed from the off-chain oracle, which was exploited — possibly by a MEV bot —

ALERT! Our system detected a series of suspicious transactions targeting <a href="/MoonwellDeFi/">Moonwell</a>’s smart contracts on #Base and #Optimism. Our analysis indicates an issue with the token price (rsETH / ETH) feed from the off-chain oracle, which was exploited — possibly by a MEV bot —
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

We’ve added two neat updates to Phalcon Explorer! 1️⃣ Direct link to swiss-knife.xyz to decode call data 2️⃣ Show Unix time for tx timestamps 🐛 Found a bug or have a feature idea? DM us or join t.me/BlockSecTeam!

We’ve added two neat updates to Phalcon Explorer!

1️⃣ Direct link to <a href="/swissknifexyz/">swiss-knife.xyz</a> to decode call data
2️⃣ Show Unix time for tx timestamps

🐛 Found a bug or have a feature idea? DM us or join t.me/BlockSecTeam!
BlockSec Phalcon (@phalcon_xyz) 's Twitter Profile Photo

.Balancer announced that it successfully executed a rescue of ~$4.1M following a new exploit path. Although detailed information has not yet been disclosed, our initial analysis indicates that the root cause may stem from a rounding-down issue in the known _upscale function.

.<a href="/Balancer/">Balancer</a> announced that it successfully executed a rescue of ~$4.1M following a new exploit path. Although detailed information has not yet been disclosed, our initial analysis indicates that the root cause may stem from a rounding-down issue in the known _upscale function.