AstraSec

118 posts

AstraSec banner
AstraSec

AstraSec

@AstraSecAI

Blockchain security auditing, trusted by Magpie, 1inch, Paraswap, Kodiak, ... (https://t.co/74XaWrdj3c)

Web3 Katılım Aralık 2023
1.3K Takip Edilen590 Takipçiler
QFEX
QFEX@QFEX·
1/ Today we’re excited to announce our $9.5M seed round, led by Yuri Sagalov (@yuris) of General Catalyst alongside Paul Graham (@paulg), @ycombinator , and a group of incredible partners and angels.
QFEX tweet media
English
96
50
494
163.6K
AstraSec
AstraSec@AstraSecAI·
Just shipped our 8th consecutive security audit report for @Listapiexyz_io ! Proud to continue securing top-tier DeFi infrastructure and supporting their ecosystem. Read the full report here: 👇 github.com/astrasecai/aud…
English
9
0
11
196
AstraSec
AstraSec@AstraSecAI·
@AnthropicAI If those companies use your service without paying or breaking down your server, it would be an attack. Are you saying all your legal clients are attacking you?
English
0
0
1
60
Anthropic
Anthropic@AnthropicAI·
We’ve identified industrial-scale distillation attacks on our models by DeepSeek, Moonshot AI, and MiniMax. These labs created over 24,000 fraudulent accounts and generated over 16 million exchanges with Claude, extracting its capabilities to train and improve their own models.
English
7.3K
6.3K
55.1K
33.6M
AstraSec
AstraSec@AstraSecAI·
We are pleased to release the security audit report for Pandora @HeyAnonai, a decentralized prediction market built for EVM-based blockchains. We’ve verified the security of their trading engine to ensure safe, efficient markets for all users. Read the full report: github.com/astrasecai/aud…
English
5
16
72
15.6K
twyne
twyne@twynexyz·
Today, Twyne finally rolls out to all @aave users. Create an instant liquidation buffer or squeeze more loops. Here's how to supercharge your Aave loans with Twyne:
twyne tweet media
English
48
45
236
44.1K
AstraSec
AstraSec@AstraSecAI·
🛡️ Exploit Analysis: YO Protocol (~$3.7M Loss) YO Protocol (@yield) suffered a slippage loss in a vault rebalance swap (3.84M stkGHO → only ~$112K USDC via Uniswap V4 pool). We decompiled the calldata: seems @yield blindly trusted the quote from @odosprotocol without confirming whether the quote result met their expectation. They've run similar ops many times successfully — but only because sizes were small. When liquidity is thin, blindly using unverified aggregator quotes is catastrophic.
AstraSec tweet mediaAstraSec tweet media
English
0
0
4
793
AstraSec
AstraSec@AstraSecAI·
🛡️ Securing the Move Ecosystem We are incredibly excited about the rapid growth of the @movementlabsxyz ecosystem! 🟡 AstraSec is proud to release the audit report for @LayerBankFi's ULAB. Our team conducted a deep-logic review to ensure a secure foundation for Move DeFi. 📑 Read the full report: github.com/astrasecai/aud…
English
0
0
3
422
AstraSec
AstraSec@AstraSecAI·
🛡️ Exploit Analysis: TMXTribe (~$1.4M Loss) On Jan 5-6, 2026, @TMXTribe on Arbitrum was exploited due to a flawed TLP token price calculation (p = AUM / total_TLP). The vulnerability shares the similar root cause as the recent @waveX_fi (x.com/waveX_fi/statu…) exploit. Swapping USDT → USDG within the vault inflates AUM without increasing total_TLP supply, artificially raising the TLP price and enabling attackers to withdraw more value than deposited. The attack followed a 4-step cycle: (1) Mint TLP tokens using USDT and stake them (2) Swap USDT → USDG through the vault (critical step!!) (3) Unstake TLP tokens to receive inflated USDT amount (4) Reverse swap USDG → USDT to complete the cycle
AstraSec tweet media
waveX 🌊@waveX_fi

Hello, this is the waveX Team. On December 6, we detected an abnormal transaction that made use of a vulnerability within part of our protocol logic. We immediately initiated a thorough investigation and mitigation procedure. We sincerely apologize for the delay in issuing this update, as we prioritized verifying the facts accurately and establishing proper measures to prevent recurrence. The impact was limited to approximately $430k after the prompt response. This issue was contained strictly within the vault-related contracts, and staking contracts and other components were not affected. waveX will fully compensate the entire loss amount. A detailed recovery plan and compensation schedule will be shared in a separate announcement shortly. Following the event, we conducted a comprehensive inspection across the protocol, which required temporarily restricting certain functionalities. The withdrawal feature for users is currently being prepared for reactivation and is scheduled to resume on Tuesday, December 16. We will provide a detailed update once it goes live. Based on the findings, we are significantly strengthening our security measures and overall defense mechanisms. We are also preparing an upgraded version of the protocol to provide a safer and more robust operating environment. All related timelines and progress updates will continue to be communicated transparently. waveX has always placed transparency and user protection as our highest priority. We are carefully coordinating internal communications to ensure that every member of our community receives clear and consistent information, and we remain fully committed to restoring your trust. Thank you for your continued support. We will return as an even safer and more resilient waveX. — waveX Team

English
1
0
3
501
AstraSec
AstraSec@AstraSecAI·
It is a classic integer overflow in the purchase/mint pricing logic of an old smart contract (deployed ~5 years ago).Most calculations used safe math (mul/sub/div), but the final addition step was done with an unsafe add — when the attacker inputs an extremely large mint amount, it overflows → calculated price drops to 0 → free minting of TRU → drain ETH from the reserve via repeated buy-dump cycles.
English
2
0
5
872
AstraSec
AstraSec@AstraSecAI·
🛡️ Exploit Analysis: Truebit Protocol (~$26M Loss) @Truebitprotocol A reminder that one missed check is all it takes. As shown in the image, the purchase function utilized SafeMath for most operations but missed the final addition step. The Vulnerability: The missing safe-add allowed an integer overflow when a large enough mint amount was passed, resulting in a token cost of zero.
AstraSec tweet media
English
5
0
19
6.1K
AstraSec
AstraSec@AstraSecAI·
@Truebitprotocol Here is root cause analysis x.com/AstraSecAI/sta…
AstraSec@AstraSecAI

🛡️ Exploit Analysis: Truebit Protocol (~$26M Loss) @Truebitprotocol A reminder that one missed check is all it takes. As shown in the image, the purchase function utilized SafeMath for most operations but missed the final addition step. The Vulnerability: The missing safe-add allowed an integer overflow when a large enough mint amount was passed, resulting in a token cost of zero.

English
0
0
7
2.8K
Truebit
Truebit@Truebitprotocol·
Today, we became aware of a security incident involving one or more malicious actors. The affected smart contract is 0x764C64b2A09b09Acb100B80d8c505Aa6a0302EF2 and we strongly advise the public not to interact with this contract until further notice. We are in contact with law enforcement and taking all available measures to address the situation. We will share updates through our official channels as they become available.
English
61
24
145
123K
AstraSec
AstraSec@AstraSecAI·
2 years ago today, we launched AstraSec with a mission to secure the most complex logic in Web3. Today, we celebrate our 2nd Anniversary! A massive thank you to the founders and protocols who have trusted us to safeguard their infrastructure. To our partners @magpiexyz_io @VeloraDEX @1inch @LayerBankFi @KodiakFi and many others—thank you for building with us. Here’s to the next chapter of security.
English
1
0
6
273
AstraSec
AstraSec@AstraSecAI·
AstraSec has successfully completed the security audit for @FriendSpaceApp. Big kudos to their team for their professionalism and commitment to building a secure ecosystem. 🤝 👇 View the findings: github.com/astrasecai/aud…
English
0
0
9
1.7K
Liquid Royalty
Liquid Royalty@liquidroyaltyX·
Just completed our first audit as we rollout our Vaults with help of @AstraSecAI and @HyacinthAudits Users will see 11%+ APY stablecoin vault + BGT boost with 200% backing very soon We will continuously work with @AstraSecAI to give the best RWA experience to users
English
1
1
21
940
AstraSec
AstraSec@AstraSecAI·
1/ The total loss amounts to approximately $1 million. The @USPD_io attack exploited a known attack vector in the deployment of ERC1967Proxy contract. The attacker front-ran the initialization call post-deployment, injecting a malicious implementation. Initially, he masked his presence by forwarding calls to the legitimate logic—biding time until the payoff was worth it. 2/ Notably, @etherscan was deceived by the attacker, making it display the official contract as the implementation. 3/ For projects using ERC1967Proxy, if proxy deployment and the initialize() call are not atomic (i.e., in the same transaction), perform a self-audit to verify the implementation contract aligns with expectations. Please check the implementation slot directly (e.g., via eth_getStorageAt) instead of trusting Etherscan's display alone. Additionally, always ensure proxy deployment and initialization occur in the same transaction to prevent front-running risks. Stay vigilant!
deebeez@deeberiroz

We @VennBuild just discovered a critical backdoor on thousands of smart contracts leaving over $10,000,000 at risk for months Along with the help of security researchers @dedaub @pcaversaccio, the seals team @seal_911 and others, we managed to rescue the majority of funds before the attacker could make their move. This is the story of how a sophisticated attacker (cough Lazarus) put backdoors in thousands of contracts and ALMOST got away with it 🧵

English
0
1
6
1.4K