<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Pike_Finance_Refund_Phishing_Attack</id>
	<title>Pike Finance Refund Phishing Attack - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=Pike_Finance_Refund_Phishing_Attack"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Pike_Finance_Refund_Phishing_Attack&amp;action=history"/>
	<updated>2026-07-26T05:17:08Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Pike_Finance_Refund_Phishing_Attack&amp;diff=5752&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/pikefinancerefundphishingattack.php}} {{Unattributed Sources}}  Pike Finance Logo/HomepagePike Finance is a loan protocol which allows loans to be taken out using collateral on other chains. After users of Pike Finance had assets locked up due to a USDC withdrawal vulnerability, and then saw the entire smart contract drained due to a botched upgrade, an advanced phish...&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Pike_Finance_Refund_Phishing_Attack&amp;diff=5752&amp;oldid=prev"/>
		<updated>2024-05-07T00:05:23Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/pikefinancerefundphishingattack.php}} {{Unattributed Sources}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Pikefinance.jpg&quot; title=&quot;File:Pikefinance.jpg&quot;&gt;thumb|Pike Finance Logo/Homepage&lt;/a&gt;Pike Finance is a loan protocol which allows loans to be taken out using collateral on other chains. After users of Pike Finance had assets locked up due to a USDC withdrawal vulnerability, and then saw the entire smart contract drained due to a botched upgrade, an advanced phish...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/pikefinancerefundphishingattack.php}}&lt;br /&gt;
{{Unattributed Sources}}&lt;br /&gt;
&lt;br /&gt;
[[File:Pikefinance.jpg|thumb|Pike Finance Logo/Homepage]]Pike Finance is a loan protocol which allows loans to be taken out using collateral on other chains. After users of Pike Finance had assets locked up due to a USDC withdrawal vulnerability, and then saw the entire smart contract drained due to a botched upgrade, an advanced phishing attack was started on the Twitter account PikeFinanc and domain pikefinance.net. After registering the fake domain and pumping the Twitter account with fake followers, the phishers responded to official updates from the Pike Finance team, claiming to be offering refunds, and pumping their posts with dozens of fake comments claiming to have received said refunds. The attack is ongoing and amount of damage is still unknown.&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&amp;lt;ref name=&amp;quot;pikefinance-13603&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;pikefinancedocs-13604&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;rektnews-13601&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;pikefinanctwitter-13612&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;pikefinance-13613&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== About Pike Finance ==&lt;br /&gt;
&amp;quot;Universal Liquidity Protocol A next generation money market  一  deposit collateral on chain A, borrow on chain B.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Pike is a universal liquidity market optimized for native assets.&amp;quot; &amp;quot;Pike is a universal liquidity market that enables lending and borrowing using native assets directly on their respective blockchains, eliminating the need for wrapping and cross-chain transfers.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Pike enables lending and borrowing using native assets directly on their respective blockchains, eliminating the need for wrapping and cross-chain transfers. For example, users can deposit Arbitrum's ARB tokens as collateral on their native Arbitrum chain, while borrowing other assets on a different blockchain.&amp;quot; &amp;quot;Pike is enabled by Wormhole Cross-Chain Messaging, Circle’s Cross-Chain Transfer Protocol, and Pyth Data Feeds.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Pike redefines the user experience for cross-chain lending and borrowing - Our focus on native assets remove the need for assets with suffixes and prefixes.&amp;quot; &amp;quot;Seamlessly maximize your yields and leverage Pike’s native cross-chain functionality  一  No longer do you have to constantly bridge your assets to explore opportunities across the ecosystem.&amp;quot; &amp;quot;Pike’s hub and spoke architecture is designed to fade into the background  一  Allowing users to realize an interconnected DeFi vision. Utilize a suite of assets from across the ecosystem  一  Ranging from yield bearing stablecoins and LSTs, to LP tokens.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Wormhole messaging eliminates risks associated with cross-chain bridges and bridged assets 一 reducing attack vectors stemming from pricing oracles.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;According to Pike Finance, the initial exploit on April 26 was caused by weak security measures in Pike's contract functions when handling CCTP transfers.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;During protocol pausing attempts, an added dependency in the code altered storage layout and moved the initialized variable, causing contract misbehavior.&lt;br /&gt;
&lt;br /&gt;
Seizing this opportunity, attackers upgraded spoke contracts without admin access, successfully siphoning off funds.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Users can now claim refund for their pre-sale deposits, we had temporarily fixed the issue, but we are still investigating.&lt;br /&gt;
&lt;br /&gt;
Get your refund:&lt;br /&gt;
http://pikefinance.net&lt;br /&gt;
&lt;br /&gt;
After getting refunded, please wait for next steps that we'll announced on our twitter.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Users can now get refunded their pre-sale deposits.After getting refund, wait for further notice from team.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This is a global/international case not involving a specific country.&lt;br /&gt;
&lt;br /&gt;
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.&lt;br /&gt;
&lt;br /&gt;
Include:&lt;br /&gt;
&lt;br /&gt;
* Known history of when and how the service was started.&lt;br /&gt;
* What problems does the company or service claim to solve?&lt;br /&gt;
* What marketing materials were used by the firm or business?&lt;br /&gt;
* Audits performed, and excerpts that may have been included.&lt;br /&gt;
* Business registration documents shown (fake or legitimate).&lt;br /&gt;
* How were people recruited to participate?&lt;br /&gt;
* Public warnings and announcements prior to the event.&lt;br /&gt;
&lt;br /&gt;
Don't Include:&lt;br /&gt;
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.&lt;br /&gt;
* Anything that wasn't reasonably knowable at the time of the event.&lt;br /&gt;
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.&lt;br /&gt;
&lt;br /&gt;
== The Reality ==&lt;br /&gt;
The Twitter account and domain are unrelated to Pike Finance. Users who interact will be asked to approve permissions to drain their wallets.&lt;br /&gt;
&lt;br /&gt;
== What Happened ==&lt;br /&gt;
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Key Event Timeline - Pike Finance Refund Phishing Attack&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|May 1st, 2024 2:26:00 AM MDT&lt;br /&gt;
|First Scam Post&lt;br /&gt;
|The first scam post is made with the malicious link, a reply to the official announcement.&lt;br /&gt;
|-&lt;br /&gt;
|May 3rd, 2024 12:15:00 AM MDT&lt;br /&gt;
|Marcus_Onyinye Comment&lt;br /&gt;
|A user named Marcus_Onyinye comments on the thread to indicate that&lt;br /&gt;
|-&lt;br /&gt;
|May 6th, 2024 5:23:14 PM MDT&lt;br /&gt;
|Phishing Still Active&lt;br /&gt;
|The phishing attack is still active and live.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Technical Details ==&lt;br /&gt;
There is no allowance to connect an empty wallet.&lt;br /&gt;
&lt;br /&gt;
== Total Amount Lost ==&lt;br /&gt;
Unknown.&lt;br /&gt;
&lt;br /&gt;
The total amount lost is unknown.&lt;br /&gt;
&lt;br /&gt;
== Immediate Reactions ==&lt;br /&gt;
One user screenshot.&lt;br /&gt;
&lt;br /&gt;
== Ultimate Outcome ==&lt;br /&gt;
The phishing attack is still happening.&lt;br /&gt;
&lt;br /&gt;
== Total Amount Recovered ==&lt;br /&gt;
None.&lt;br /&gt;
&lt;br /&gt;
There do not appear to have been any funds recovered in this case.&lt;br /&gt;
&lt;br /&gt;
== Ongoing Developments ==&lt;br /&gt;
Investigation?&lt;br /&gt;
== Individual Prevention Policies ==&lt;br /&gt;
{{Prevention:Individuals:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Individuals:End}}&lt;br /&gt;
&lt;br /&gt;
== Platform Prevention Policies ==&lt;br /&gt;
{{Prevention:Platforms:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Platforms:End}}&lt;br /&gt;
&lt;br /&gt;
== Regulatory Prevention Policies ==&lt;br /&gt;
{{Prevention:Regulators:Placeholder}}&lt;br /&gt;
&lt;br /&gt;
{{Prevention:Regulators:End}}&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&amp;lt;ref name=&amp;quot;pikefinance-13603&amp;quot;&amp;gt;[https://www.pike.finance/ Pike | Universal Liquidity Protocol] (May 6, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;pikefinancedocs-13604&amp;quot;&amp;gt;[https://docs.pike.finance/ Introduction to Pike | User Docs | Pike] (May 6, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;rektnews-13601&amp;quot;&amp;gt;[https://rekt.news/pike-rekt/ Rekt - Pike Finance - Rekt] (May 6, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;pikefinanctwitter-13612&amp;quot;&amp;gt;[https://twitter.com/PikeFinanc @PikeFinanc Twitter] (May 6, 2024)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;pikefinance-13613&amp;quot;&amp;gt;[https://pikefinance.net/ https://pikefinance.net/] (May 6, 2024)&amp;lt;/ref&amp;gt;&amp;lt;/references&amp;gt;&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>