OShield 🛡️
308 posts

OShield 🛡️
@oshield_io
Smart Contract Auditing and Security Services 🛡️





We completed an audit of @DeFiTuna ‘s leveraged product. 2 critical vulnerabilities were identified alongside a number of high and medium severity level issues. All bugs have been patched and fixes are implemented. Tuna is safely deployed on top of @FusionAMM markets and @orca_so whirlpools. Read the full report on our publications page 👇


We are happy to see the return of all the funds in the recent @loopscale incident to their customers and treasury. We highlight that the incident was part of a code that was deployed after our audit and was out of our audit scope. We command the team on their response and communication during this experience. @oshield_io is looking forward to continue our support for @loopscale and our other partners on their security needs for a more safe robust DeFi ecosystem.






Fusion AMM is proud to announce its readiness to move out of BETA, supported by two successful audit reports conducted by industry-leading auditors.



We are happy to see the return of all the funds in the recent @loopscale incident to their customers and treasury. We highlight that the incident was part of a code that was deployed after our audit and was out of our audit scope. We command the team on their response and communication during this experience. @oshield_io is looking forward to continue our support for @loopscale and our other partners on their security needs for a more safe robust DeFi ecosystem.


Today at 11:30AM EST, a manipulation of Loopscale’s RateX PT token pricing functions led to an exploit of ~5.7M USDC and 1,200 SOL from the Loopscale USDC and SOL Vaults. All Loopscale markets have been temporarily halted while our team investigates further. This exploit represents roughly ~12% of funds on Loopscale and only affects depositors to the Loopscale USDC and SOL vaults. This does not affect borrowers or loopers. We are working to resume repayment functionality as soon as possible to mitigate unforeseen liquidations. We are working with law enforcement officials, security professionals, and our investors to recover funds. We will release additional information and a full technical post-mortem as soon as we have it.

✅ The audit of XDEX, involving staking, and farming smart contracts is now complete. We reviewed the entire protocol suite to ensure security and reliability. 🔗 Read the full report here: github.com/oshieldio/Publ…



Introducing the Unstake Pool - Instant Liquidity for Your Staked Assets We are excited to launch Unstake Pool, a powerful new way to unstake your LSTs instantly - no delays, no cooldowns. Whether you are reacting to fast-moving markets or just want liquidity now, Unstake Pool gives you immediate access to SOL in exchange for a small, dynamic fee. 1/5

📰 INCIDENT REPORT As all of you already know, Cetus recently experienced a smart contract exploit targeting our CLMM pools. Today we are releasing our full incident report to provide transparency into our response, including the root cause, learnings, and next steps. We deeply appreciate the community’s patience and support during this challenging time. Together, we will rebuild a stronger and more secure Cetus. 🙏 💪 Full report here: [cetusprotocol.notion.site/Cetus-Incident…]

@CetusProtocol vulnerability today: When you shift a 256-bit number left by 64 bits (same as multiplying by 2⁶⁴), you need to make sure the number doesn’t already use the top 64 bits (bits 192–255) — because shifting will push those bits beyond the 256-bit limit, causing overflow. The Cetus math library tried to check for overflow, but it only rejected numbers where all of the top bits were 1 — a coarse check. It missed cases where just one bit (like bit 192) was set to 1. That single bit, when shifted by 64, would silently overflow. A simple check like (n >> 192) != 0 would’ve caught it. Tiny miss. Big vulnerability.






