HypernativeLabs

An attempted exploit on @ParallelMoney’s vaults was stopped automatically today. Hypernative detected the pattern and paused the relevant contracts within seconds. No funds lost. This comes after a brutal stretch for onchain security. April alone saw major incidents at Drift and KelpDAO, part of a wider surge in successful exploits. Attackers are coming prepared. The difference, increasingly, is whether the protocols are too. Credit to the Parallel team for having the monitoring and automated response in place before it was needed. That’s the work that doesn’t make headlines until it does.

A DeFi protocol was exploited. Clearstar Labs had funds in it. By the time they got the alert, the exit had already executed automatically. Funds safe. That's what real-time monitoring plus automated response looks like when it works. Wintermute, Wave, and Clearstar break down how they build it: buff.ly/iH6SEOA

When did institutions last stop a hack by reading a report after the fact? Uli Dell'Orto, CRO at Hypernative, made the case at Consensus Miami that the security stack for onchain institutions needs to go well beyond what any single control can provide. Audits, screeners, compliance tools: each plays a role. But without continuous monitoring of onchain and offchain signals, and the ability to execute automated responses in real time, the gaps between those controls become the attack surface. Over the past three years, that approach has helped prevent over $3B in hacks and exploits across Hypernative's customer base. The next threat is already forming: AI-led attacks. The question is not which tool you trust. It is whether they work together fast enough. Learn more at buff.ly/6jnXSP3

@Zebec_HQ 🫡

As Zebec continues to scale, security remains a top priority across our ecosystem. Since integrating with @HypernativeLabs, more than 50,000 wallets have been screened across our product suite. Hypernative helps strengthen our infrastructure with AI-powered monitoring and real-time threat prevention across onchain and offchain environments.

The FBI's annual internet crime report puts crypto-related fraud at more than half of all internet crime losses. Not half of crypto crime. Half of all internet crime. Legacy compliance providers are working from off-chain data sources with multi-hour or multi-day tagging delays. New wallets spin up constantly. Bad actors move across chains to obscure activity. The tooling that works for traditional payments does not map to this environment. Real-time fraud scoring is not optional infrastructure. It is the baseline requirement. Our recent webinar with @reown_, @reserveprotocol and @wavedigital_ goes deep on what real-time onchain detection actually requires, and why the compliance tooling most institutions already have is not sufficient on its own. Watch the full recording on demand: buff.ly/zQcPxU7

Banks and asset managers are moving onchain. The security frameworks they built for custodial finance won't protect them there. We broke down what a real institutional security stack looks like: custody, protocol due diligence, transaction security, real-time monitoring, compliance screening, and incident response. Each layer matters. A gap in any one of them creates exposure the others can't cover. From our Ultimate Guide to Web3 Security: buff.ly/WlP3d89

What if the thing that makes blockchain trustworthy is also what makes it dangerous? Transparency in onchain systems cuts both ways. When an attacker can see your address, your holdings, your transaction history, and your exposure to other protocols, they have everything they need to build a targeted strategy against you. Dan Caspi, CTO at Hypernative, broke this down at Consensus Miami, describing transparency as a ladder with distinct rungs: who you are, how you behave, and what you hold. Each layer of visibility is a potential attack surface. The fix is not less transparency across the board. It's understanding which layer you're exposing, to whom, and whether that exposure serves you or someone else. Learn more at https://www.buff.ly/6jnXSP3

Lighting up the Dark Forest Onchain w/ Dan Caspi & Weso - The Cap Room Episode #3 On this episode we have on the CTOs of @HypernativeLabs and Cap, @gbvpzffd2r & @the_weso, and we dive into how security practices onchain have evolved over the past half decade, how Hypernative's auto-pause feature stops exploits before they happen, and where DeFi can improve in order for their to be a safer onchain world for everyone. Enjoy!

Hypernative's Dan Caspi (@gbvpzffd2r) joins @the_weso in The Cap Rooms for a conversation on the evolution of onchain security. Definitely worth your time. Thanks for have us @CapApp!

When it comes to security, every second counts. That's why Cap has partnered with @HypernativeLabs to implement auto-pause, a system that automatically stops all platform activity the moment a threat is detected. No delays. No hoping for the best. Just instant protection.

The wallet that can pause your protocol should never be the wallet that can upgrade it. @Pybast, CTO of @Corkprotocol, walked through this at the Rekt Security Summit in Cannes. Giving Hypernative the pause role makes sense for rapid response. But if that role also carries upgrade permissions, you have introduced a new attack vector instead of closing one. The same logic applies to unpause. If the key that unpauses your protocol gets exfiltrated, an attacker can trigger a pause, wait, unpause, and exploit again. These are governance design decisions that need to happen before you integrate any security tooling. Learn more at buff.ly/ERwOrHs

The Kelp DAO bridge failed in one transaction. The cascade on Aave took 46 minutes. WETH suppliers who detected the utilization spike early still had a window to withdraw. Those who found out hours later could not move at all. The bridge failure is a security story. What happened to Aave over the next 46 minutes is a risk management story. They require different responses. Our latest piece maps where the institutional monitoring gap shows up in practice: forced liquidations, borrow rate spikes, LP composition drift, staking risk, and the systemic signals that large liquidation events send to the whole market. buff.ly/82CinoS

DAS London, after hours. Join Hypernative tomorrow at The Liquidity Lounge Cocktail Hour for drinks, light bites, and a room full of builders, operators, and institutional players moving the market forward. Private event. RSVP required. buff.ly/tlyTvtw

The pools are curated by @Re7Labs and are fully isolated. Exposure is limited to Bitcoin assets and native USDC. Onchain monitoring by @HypernativeLabs is active. If unusual activity is detected, the pool is automatically paused.

@HOSS_ibc contact [at] hypernative [dot] io

@HypernativeLabs What is the best way to get in touch with you guys? I received an email and want to verify its legit. (can't dm on here)

"If a transaction looks simple, it's probably safe." A straightforward token transfer can embed unexpected approvals, delegate permissions to malicious contracts, or route funds through impersonated intermediaries. None of that is visible in a raw transaction payload. buff.ly/6upQJWl

Full house in Miami. Thanks to @HypernativeLabs and @zeroshadow_io for co-hosting a poker night with us at Consensus, and to everyone who came through. Similar VIP events to come.

.@PancakeSwap, one of the leading DEXs in the industry, has deployed Hypernative to monitor its smart contract infrastructure across multiple blockchains. After evaluating several monitoring providers, PancakeSwap chose Hypernative for real-time exploit detection, low false positive rates. Read the full announcement: buff.ly/8wS1iTK

This is @Ikigaieuh, Smart Contract Engineer at @Neutrl, on building security into NUSD from the ground up with Hypernative. Read the full breakdown: buff.ly/ie8r7pK

#HSCLifeRules - Shawn Lim, VP of Asia at @HypernativeLabs, HSC Asset Management Hong Kong, April 23 We've seen internal fat fingers from some of the largest names out there - someone minted four hundred trillion stablecoins. Those could have been prevented. Now add AI agents to the picture: how do you build guardrails around systems that can turn rogue? "Every time a new model drops, we see a spike in hacks. The velocity of exploits increases. That builds the case for more layers of defense - institutional-grade security, the CloudFlares and CrowdStrikes of blockchain" #HSCAssetManagement