Bitcoin Forum
November 20, 2026, 04:56:23 PM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: A question regarding wrapped tokens  (Read 21 times)
noorman0 (OP)
Hero Member
*****
Offline

Activity: 2198
Merit: 892


[Nope]No hype delivers more than hope


View Profile WWW
Today at 01:12:12 PM
 #1

I recently came across news about a wrapped token on the Hyperliquid network (XMR1) that was hacked.
Quote
HYPERLIQUID WRAPPED MONERO APPEARS TO BE GETTING HACKED!

@lookonchain flagged an attacker wallet that received 5.2 million $XMR1, dumped it on Hyperliquid, then used the proceeds to buy $ETH.

So far the address has spent $13.22M USDC for 7,467 $ETH.

$XMR1 is the Hyperliquid-wrapped version of Monero that lets people trade $XMR exposure on the exchange through the Wagyu bridge. It’s not official Monero.
Source

This raises the question: how is this resolved?
- Attempting to freeze the assets at the attacker's end seems difficult, as the attacker has already bridged the funds across different network.
- If Wagyu (the issuer of the wrapped token) mints new tokens, the existing tokens (sold) in circulation become unbacked (to the detriment of the holders).

This incident does not affect the price of the original coin on its native network.

██████████████████████████████████████████████████████████████████████████
███▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
██████████████▄▄██████████████████████████████████████████████████████████
█████████████████▄████████████████████████████████████████████████████████
█████████▀▀▀▀███████████▄▄▄▄▄████████▄▄▄▄▄▄██▄▄▄▄▄▄▄▄▄▄▄██████████████████
█████████████▐███████▄█████████▄███▄██████████████████████████████████████
█████████▄▄▄▄█████▀█████████████████████▀▀▀███████████████████████████████
█████████████████▀██████████████████████████████▀███▀█████████████████████
████████████████▄███████████████▀███████████████▄███▄█████████████████████
███████████▀████████▀████▄▄▄▄▄▄▄██████████████████████████████████████████
████████████▀████████▀████████████████████████████████████████████████████
███▀▀▀▀▀▀██████▀▀▀▀█████▀▀▀▀▀▀▀▀███▀▀▀▀▀█████▄▄▄▄▄▄▄▄▄▄▄███▀▀▀▀▀██▀▀▀▀▀███
██████████████████████████████████████████████████████████████████████████


..FARM YOUR AIRDROP ➜.
asriloni
Legendary
*
Offline

Activity: 3934
Merit: 1174


Leading Crypto Sports Betting & Casino Platform


View Profile
Today at 03:33:07 PM
 #2

I recently came across news about a wrapped token on the Hyperliquid network (XMR1) that was hacked.
Quote
HYPERLIQUID WRAPPED MONERO APPEARS TO BE GETTING HACKED!

@lookonchain flagged an attacker wallet that received 5.2 million $XMR1, dumped it on Hyperliquid, then used the proceeds to buy $ETH.

So far the address has spent $13.22M USDC for 7,467 $ETH.

$XMR1 is the Hyperliquid-wrapped version of Monero that lets people trade $XMR exposure on the exchange through the Wagyu bridge. It’s not official Monero.
Source

This raises the question: how is this resolved?

- Attempting to freeze the assets at the attacker's end seems difficult, as the attacker has already bridged the funds across different network.

- If Wagyu (the issuer of the wrapped token) mints new tokens, the existing tokens (sold) in circulation become unbacked (to the detriment of the holders).

This incident does not affect the price of the original coin on its native network.

The only possible thing for Wagyu to reimburse the lose. I don't see a better way than this.



As per someone from Wagyu, all of user's lost will be refunded, but i'm doubting this, though this is the only way to solve this, and let the new wrapped token still remain pegged to the its old underlying when they're migrating it.

Wagyu is not a big platform, and they were not even generating 1 million revenue, and it makes no sense if they can refund all of people who lost due to the stupidity by let the data still exist in the hacked old server.

But if he (i refer someone who was in the tweet) can't refund, the XMR1 will remain unbacked forever. Issuing the new wrapped token is just complicating the situation.




██████████████████████████████████████████████████████████████
████████████
▀▀███████▀████████████████████████████████████████
██████████
▀██▄▄████▄██▐████▀▀███████████▀▀████████████████████
█████████
▌██▐██████▌██████▌█▐█████████████▐███████████████████
█████████
▌█████████▄▄▄██████▀▀▀▀███████▌█████▀████████████████
██████████
▄███▀███████▀▀██████▄██████████▐█▀█▄███▀▀███████████
████████████
▄▄███▀▀██▄▄▄▄██▐███▀██▄█▐█▌██▀█▄██▀██▄▄███████████
████████████████
▄▄███▀██▌███████▄█▌███████▐██▌███▀█▄██████████
██████████
▀███▄███████████▐██▌█▐████████▐██▐████▄██▀██████████
█████████
▌██▄███████████▄████▄████▄██▄██████▀▄█████▄▀█████████
█████████
▌██▀███▀▀███▄█████████████████████▄██▀▀▀▀▀█▄█████████
██████████
▄██████▄▄██████████████████████████▄▄▄▄▄▄███████████
██████████████████████████████████████████████████████████████
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██

 🎰  🎲 ..Play Smarter.. 🏀  ⚽ ..Play Now..
elda34b
Sr. Member
****
Offline

Activity: 1176
Merit: 357


View Profile
Today at 04:14:04 PM
 #3

due to the stupidity by let the data still exist in the hacked old server.
I think that's on the hosting part instead of them tbf. Based on their story, if those data were deleted (as in the deployer delete it and the hosting also delete the files and logs, or whatever data exist), then it's unlikely the hacker will get the data. Though I'm not sure how they confirmed that the server still keeps the data after this case went up unless they have a discussion with the 1984 hoster mentioned above. CMIIW.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!