HypernativeLabs

1.6K posts

HypernativeLabs banner
HypernativeLabs

HypernativeLabs

@HypernativeLabs

Detect and neutralize Web3 threats in real time. 200+ dApps, chains, wallets, and financial institutions rely on Hypernative to prevent hacks, exploits & fraud.

Katılım Ekim 2022
133 Takip Edilen15.4K Takipçiler
Sabitlenmiş Tweet
HypernativeLabs
HypernativeLabs@HypernativeLabs·
.@Bitwise is expanding deeper into DeFi. With $15B+ in AUM, they’re launching new vault infrastructure on @Morpho and increasing direct onchain participation across allocation strategies, collaterals, and protocol interactions. To support that shift, Bitwise has selected Hypernative to integrate real-time exploit detection and automated response into their DeFi operations. As asset managers move from passive exposure to actively operating vaults, risk management must operate at the same speed as the market. We’re proud to support Bitwise as they scale institutional-grade DeFi strategies with built-in capital protection. Read the full announcement: buff.ly/DO1EUC6
HypernativeLabs tweet media
English
24
9
72
49.9K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
The Bybit attack did not look like an attack from the inside. The interface looked right. The workflow looked right. The team signed what appeared to be a routine transaction. What was happening onchain was something else entirely. Malicious approvals were granted. The funds were gone before anyone understood what had happened. Blind signing is not a UX problem. It is a security failure. And stablecoin programs running at institutional scale cannot afford to get this wrong. At our recent webinar, guests from @reown_, @reserveprotocol and @wavedigital_ weigh in on what better signing infrastructure looks like from the wallet and institutional sides. Watch the full recording on demand: buff.ly/zQcPxU7
English
0
0
0
211
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Wasabi Perp drained $5M+ across Ethereum, Base, and Blast this morning. No smart contract bug. No oracle manipulation. No exploit primitive. A single private key held admin authority across all three chains. Once it was compromised, the protocol drained itself through its own privileged functions in two hours. How each stage could have been stopped: → Drainer deployment: Hypernative's detection engine flagged the attacker's orchestrator contract three minutes before the first drain. A pre-configured response would have paused vaults before a single transaction settled. → Privilege escalation: A monitor on RoleGranted events that checks every admin grant against a pre-approved destination list flags the attack the moment it begins. Unscheduled grants from a known admin wallet are the clearest possible signal of key compromise. → Vault drain: A strategy whitelist on strategyDeposit blocks any call routing collateral to an unrecognized address. The attacker's stub never receives funds, no matter who signs the transaction. → Pool implementation swap: An upgrade governance policy blocks any upgradeToAndCall to an implementation that has not been pre-authorized. The pool's code cannot flip to attacker bytecode in the same block the proposal is made. The contracts behaved exactly as written. Every signature was valid. The trust model was the gap. Full breakdown: buff.ly/BgZjezx
HypernativeLabs tweet media
English
2
0
3
451
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Off-chain messages still move money. If you treat permits as “lightweight,” you’re creating a blind spot. This clip from our recent webinar with @safe talk about how to handle the risks inherent in offchain permits. ▶️ Watch the full recording here: hypernative.io/events-webinar…
English
0
0
4
209
HypernativeLabs
HypernativeLabs@HypernativeLabs·
What does a $19B liquidation event in 20 minutes tell you about the state of risk management in crypto? Marshall Lipman, VP of Strategy at Hypernative, was on the "What Happened on 10/10?" panel @ParisBlockWeek alongside senior leaders from Bitwise, Xapo Bank, and Paribu. His read: October 10th exposed a fundamental gap. Institutional clients were deployed across dozens of protocols and chains, borrowing against volatile assets and chasing yield in stablecoins, but had no real-time systemic view of how their positions were connected. When everything started unwinding at once, the speed of collapse outpaced any manual response. The institutions that fared best had automated monitoring in place before the event, not after it. Hypernative works with 50-plus asset managers to provide continuous market risk monitoring across 75-plus blockchains. October 10th was a live stress test of that infrastructure. Learn more at buff.ly/yt4nQW0
English
2
0
13
2K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Here is a deep dive into the Wasabi Perp exploit: how the attack unfolded, what failed, and how it could have been prevented at each step. hypernative.io/blog/when-the-…
HypernativeLabs tweet media
HypernativeLabs@HypernativeLabs

🔴 Wasabi Perp Drained for ~$5M+ Across Three Chains via Deployer Key Compromise This morning at 07:48 UTC, Hypernative detected an active exploit targeting Wasabi Perp across three chains. Approximately $5M+ was drained from the protocol's vaults and long pools in a coordinated ~2-hour attack window. Hypernative's systems fired high-severity alerts in real-time across all three chains involved (Ethereum, Base, Blast) as the vault drains and pool upgrade executed surfacing the privileged strategyDeposit calls and malicious implementation swap as they happened. Note: Wasabi is not a Hypernative customer. What happened: → The attacker gained control of the Wasabi Deployer EOA (the sole admin key across every chain's PerpManager) and used it to grant admin authority to an attacker-controlled contract. → From there, they called strategyDeposit across 8 WasabiVault proxies to redirect collateral, then performed a UUPS upgrade on the WasabiLongPool to an attacker-deployed implementation, sweeping the pool's balances. → The same playbook was replicated on Base and Blast. The compromised key has not been rotated; LongPool contracts on Ethereum and Base remain under attacker control. ❗ If you have funds or approvals in Wasabi Perp on any chain act now: → Revoke all approvals → Withdraw any remaining funds immediately We will publish a full technical analysis shortly.

English
1
2
12
2.4K
HypernativeLabs retweetledi
Pharos | Mainnet Arc
Pharos | Mainnet Arc@pharos_network·
Pharos Pacific Ocean Mainnet is LIVE! ⚓ The first asset-native, institution-grade L1 engineered for high performance and regulatory compliance, bridging the gap between deep liquidity and real-world impact Today, Pharos sets sail for the global stage 🌊
English
341
239
819
151.2K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
🔴 Wasabi Perp Drained for ~$5M+ Across Three Chains via Deployer Key Compromise This morning at 07:48 UTC, Hypernative detected an active exploit targeting Wasabi Perp across three chains. Approximately $5M+ was drained from the protocol's vaults and long pools in a coordinated ~2-hour attack window. Hypernative's systems fired high-severity alerts in real-time across all three chains involved (Ethereum, Base, Blast) as the vault drains and pool upgrade executed surfacing the privileged strategyDeposit calls and malicious implementation swap as they happened. Note: Wasabi is not a Hypernative customer. What happened: → The attacker gained control of the Wasabi Deployer EOA (the sole admin key across every chain's PerpManager) and used it to grant admin authority to an attacker-controlled contract. → From there, they called strategyDeposit across 8 WasabiVault proxies to redirect collateral, then performed a UUPS upgrade on the WasabiLongPool to an attacker-deployed implementation, sweeping the pool's balances. → The same playbook was replicated on Base and Blast. The compromised key has not been rotated; LongPool contracts on Ethereum and Base remain under attacker control. ❗ If you have funds or approvals in Wasabi Perp on any chain act now: → Revoke all approvals → Withdraw any remaining funds immediately We will publish a full technical analysis shortly.
English
0
4
12
3K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
The three most common wallet-level attacks right now all share something in common: they look completely normal at the moment the user encounters them. Drainer contracts request standard-looking approvals. Poisoned addresses sit inside the user's own transaction history. Scam tokens arrive uninvited and mimic legitimate projects. None of them trip a blocklist. None of them fail a visual check. That's the point. We broke down how each one works and why most wallet defenses miss them. Check the slides, and download The Ultimate Guide to Web3 Security for the full picture. hypernative.io/resources/ulti…
English
6
6
27
1.6K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Thresholds don’t stop signer compromise. Operational discipline does. This clip from our recent webinar with @safe breaks down how to reduce signer risk in practice. ▶️ Watch the full recording here: hypernative.io/events-webinar…
English
1
0
8
858
HypernativeLabs
HypernativeLabs@HypernativeLabs·
$19B in leverage positions were wiped out in less than 20 minutes. It happened on a Friday, after US market close, at the least liquid point in the trading week. @wavedigital_ was monitoring every liquidity pool in DeFi with Hypernative agents tracking de-peg risk, pool imbalances, and position thresholds in real time. When the cascade started, they had a plan. Many others were improvising. In a 20-minute window, there is no time to figure out what to do. At our recent webinar, we get into exactly how Wave set up their monitoring and response framework, and what that looked like on one of the worst days in recent crypto market history. Watch the full recording on demand: buff.ly/zQcPxU7
English
2
0
6
739
HypernativeLabs
HypernativeLabs@HypernativeLabs·
The question for wallet builders and payment platforms: Are you flagging threats before the transaction, or after the damage is done? Guillermo Muñoz on why pre-transaction simulation changes the calculus for onchain security at @WalletConnect's WalletCon 2026. Learn how Hypernative Wallet Protect secures every transaction before it lands: buff.ly/OrIp9F9
English
1
4
13
775
HypernativeLabs
HypernativeLabs@HypernativeLabs·
.@bravaxyz, a non-custodial portfolio management platform for professional capital allocators, has selected Hypernative to provide real-time monitoring across its DeFi lending pool infrastructure. Brava routes capital into hundreds of overcollateralized lending pools across Ethereum, Base and Arbitrum. As new collateral types and protocol interactions shift the risk surface continuously, block-level monitoring becomes essential. With Hypernative Platform, Brava gains automated threat detection for depeg signals, collateral health, exploit-level risks and suspicious onchain activity, with alerts routed directly into their systems via API. Read the full announcement: buff.ly/2u3qU0p
HypernativeLabs tweet media
English
1
2
8
978
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Hypernative generated an alert 15 minutes before the first hack transaction against Cork Protocol. That sounds like a lot of time. It wasn't. Fifteen minutes to validate the alert, reach the affected team, mobilize security researchers, and coordinate a response. José Cardoso walked through what that window actually looks like from the inside at the Rekt Security Summit in Cannes. The real question for any protocol: when an alert fires, do you have a plan or are you improvising? Learn more at buff.ly/fIItDxk
English
3
8
8
1.1K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Onchain systems don’t get to separate product design from risk design. The rules of the market, the timing of settlement, and the response layer all become part of the same trust architecture. Proud to be part of Royco's stack 🤝
Royco@roycoprotocol

Royco partners with Hypernative for real-time monitoring. @HypernativeLabs provides continuous on-chain monitoring with automated threat detection across every transaction and contract interaction. The platform protects over $100 billion in digital assets across 75+ chains, has detected 99.5% of all hacks with a false positive rate below 0.001%, and has saved more than $3 billion in customer funds. Royco Dawn's monitoring integrates directly with the protocol's emergency response plan. If anything abnormal is detected, the system is built to act, not just alert. Coupled with a minimum settlement delay of 24 hours for all user and admin operations, Hypernative’s continuous monitoring will allow Royco to preemptively stop any exploit before it is executed. Audits verify code at deployment. Hypernative monitors what's happening right now. To the Hypernative team: thank you. Your real-time layer is a core part of what makes Royco Dawn something users can trust not just at launch, but every day after.

English
4
1
9
1.1K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Giving a third-party the ability to pause your protocol is a big decision. This is @Neutrl's reasoning on why they gave Hypernative a pauser role. Critical and high-severity alerts trigger an automated pause. Lower-severity signals go to manual review. The monitoring covers Neutrl's own contracts, Ethena, Sky and Pendle on mainnet, and CEX activity feeds -- visibility across the full collateral and yield stack the protocol depends on. Read the full case study: buff.ly/lEZ80sv
HypernativeLabs tweet media
English
3
3
13
1.2K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Blocklists catch known threats. Transaction simulation catches hidden ones. But most wallet users still rely on a set of assumptions that do neither. We broke down four of the most common wallet security myths and what actually closes the gap. buff.ly/k1Ytx1P
HypernativeLabs tweet media
English
3
1
4
608
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Hypernative's VP of Asia Shawn Lim joined a strong lineup of speakers at the HSC Asset Management conference in Hong Kong last week, alongside leaders from BlackRock, HSBC, Fidelity, EY, Bloomberg and others. Great to see Hypernative represented in one of APAC's key conversations on digital assets and institutional infrastructure.
HypernativeLabs tweet media
English
1
1
5
860
HypernativeLabs
HypernativeLabs@HypernativeLabs·
No one is bulletproof against a state-sponsored attacker. But the gap between 'vulnerable' and 'defenseless' is enormous. Continuous monitoring. Automated policy enforcement. Threat detection that runs before the transaction lands. You need people whose full-time job is this. Build that team in-house, or work with one that already exists.
Haseeb >|<@hosseeb

Read this. Remember, Lazarus are professionals. They are an efficient state-backed organization that does this for a living. If you want to stand a chance, you must defend like it's your full-time job. Because for them, it is.

English
2
4
9
2.8K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Hypernative has integrated @Lukka's address attribution data into its risk intelligence infrastructure, adding another data source to the broad set of signals, proprietary detections, and ML models the platform already uses to protect more than $100B in digital assets across 75+ chains. The integration expands entity-level attribution coverage across Ethereum, Bitcoin, Tron, and Solana, enriching risk categorization across sanctions, scams, hacks, darknet marketplace activity, and more. Read more: buff.ly/pvXXptQ
HypernativeLabs tweet media
English
4
1
8
1.3K
HypernativeLabs
HypernativeLabs@HypernativeLabs·
Most hacks follow one of two patterns: a multi-transaction setup with a sleeper contract, or a single atomic transaction that drains everything at once. The Cork Protocol exploit was both. Unusual onchain activity preceded a single transaction that stole $12M. Traditional monitoring would have caught the signal but not stopped the execution. José Cardoso, Head of BD at Hypernative, broke down the anatomy at the Rekt Security Summit in Cannes. Learn more at buff.ly/7YgmpSn
English
1
2
3
2.3K