Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/fengshoungfsdelegatecallreservesattack.php}} {{Unattributed Sources}} Generic ImageIt is unclear the intent behind the launch of the NGFS (FENGSHOU) token, however it most likely wasn't to give an attacker full access to take all of the liquidity. A couple days after the token launched on April 23rd, an exploit took advantage of a delegateCallReserves vulnerabili..."

2024-05-16T19:24:30Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/fengshoungfsdelegatecallreservesattack.php}} {{Unattributed Sources}} thumb|Generic ImageIt is unclear the intent behind the launch of the NGFS (FENGSHOU) token, however it most likely wasn't to give an attacker full access to take all of the liquidity. A couple days after the token launched on April 23rd, an exploit took advantage of a delegateCallReserves vulnerabili..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/fengshoungfsdelegatecallreservesattack.php}}
{{Unattributed Sources}}

[[File:Binancesecurity.jpg|thumb|Generic Image]]It is unclear the intent behind the launch of the NGFS (FENGSHOU) token, however it most likely wasn't to give an attacker full access to take all of the liquidity. A couple days after the token launched on April 23rd, an exploit took advantage of a delegateCallReserves vulnerability, which allowed the attacker to set whatever library smart contract he wanted, including a malicious one which transferred all the liquidity to themselves.

This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-13740" /><ref name="ddimitrovv22twitter-13838" /><ref name="moralismoney-13839" /><ref name="web3-13840" /><ref name="bscscan-13841" /><ref name="bscscan-13842" /><ref name="bscscan-13843" /><ref name="bscscan-13844" /><ref name="bitqueryexplorer-13845" /><ref name="listingspy-13846" /><ref name="coinmarketcap-13847" />

== About FENGSHOU (NGFS) ==
"Shortly after the deployment of the FENGSHOU (NGFS) token, it was attacked, resulting in a loss of approximately $191,000. The vulnerability lies in a public `delegateCallReserves` function which allows the attacker to set an arbitrary address to a UniSwapV2 proxy."

"The FENGSHOU (NGFS) Token was hacked shortly after deployment. The attack was a simple 3-step process which was possible because the deployer didn't initialize the contract properly.

1. The attacker called `delegateCallReserves` which sets the uniswapV2Proxy to msg.sender."

"2. Then it was easy for the attacker to set the `_uniswapV2Library` to any address he wants and to be able to call the third critical function."

"3. The `reserveMultiSync` allowed him to sync(transfer) all of the funds from the PancakeSwap BSC-USD - NGFS pool to his address. And just like that ~$191k has been affected."

"The data of the token and the pair are no longer updated as the token is SCAM" "Very high start liquidity, it looks like a scam!"

This is a global/international case not involving a specific country.

The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.

Include:

* Known history of when and how the service was started.
* What problems does the company or service claim to solve?
* What marketing materials were used by the firm or business?
* Audits performed, and excerpts that may have been included.
* Business registration documents shown (fake or legitimate).
* How were people recruited to participate?
* Public warnings and announcements prior to the event.

Don't Include:
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
* Anything that wasn't reasonably knowable at the time of the event.
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.

== The Reality ==
This sections is included if a case involved deception or information that was unknown at the time. Examples include:

* When the service was actually started (if different than the "official story").
* Who actually ran a service and their own personal history.
* How the service was structured behind the scenes. (For example, there was no "trading bot".)
* Details of what audits reported and how vulnerabilities were missed during auditing.

== What Happened ==
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.
{| class="wikitable"
|+Key Event Timeline - FENGSHOU (NGFS) DelegateCallReserves Attack
!Date
!Event
!Description
|-
|April 23rd, 2024 3:45:54 AM MDT
|Smart Contract Creation
|The vulnerable smart contract is first created.
|-
|April 25th, 2024 5:18:05 AM MDT
|Exploit Transaction
|The exploit transaction happenc on the Binance Smart Chain.
|-
|April 26th, 2024 1:53:37 AM MDT
|Smart Contract Recreated
|The NGFS smart contract is recreated at a new blockchain address.
|-
|April 26th, 2024 2:33:00 AM MDT
|ImmuneBytes Analysis
|ImmuneBytes publishes an analysis of the exploit including the transaction and the cause in a Tweet.
|-
|April 26th, 2024 8:20:00 AM MDT
|ListingSpy Scam Report
|ListingSpy claims the new version of the token is a scam, due to the high starting liquidity.
|-
|April 27th, 2024 8:08:00 AM MDT
|Technical Analysis Published
|ddimitrov22 publishes a technical analysis of the FENGSHOU exploit, which is attributed to a simple failure to initialize the smart contract correctly.
|}

== Technical Details ==
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

== Total Amount Lost ==
The total amount lost has been estimated at $190,000 USD.

How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?

== Immediate Reactions ==
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?

== Ultimate Outcome ==
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?

== Total Amount Recovered ==
There do not appear to have been any funds recovered in this case.

What funds were recovered? What funds were reimbursed for those affected users?

== Ongoing Developments ==
What parts of this case are still remaining to be concluded?
== Individual Prevention Policies ==
{{Prevention:Individuals:Placeholder}}

{{Prevention:Individuals:End}}

== Platform Prevention Policies ==
{{Prevention:Platforms:Placeholder}}

{{Prevention:Platforms:End}}

== Regulatory Prevention Policies ==
{{Prevention:Regulators:Placeholder}}

{{Prevention:Regulators:End}}

== References ==
<references><ref name="slowmisthackedarchive-13740">[https://web.archive.org/web/20240513181718/https://hacked.slowmist.io/?c=&page=2 SlowMist Hacked - SlowMist Zone] (May 13, 2024)</ref>

<ref name="ddimitrovv22twitter-13838">[https://twitter.com/ddimitrovv22/status/1784223165251489952 @ddimitrovv22 Twitter] (May 16, 2024)</ref>

<ref name="moralismoney-13839">[https://moralismoney.com/chain/binance/token/price/fengshou-2 FENGSHOU (NGFS) Price Today | Real-Time On-Chain Metrics | Moralis Money | Discover & Trade Undervalued Altcoins] (May 16, 2024)</ref>

<ref name="web3-13840">[https://web3.bitget.com/ar/swap/bnb/0xe8a11cB7671ebcB9bcAEeDad449FE02683b585d6 $0.{3}1704 | تبديل FENGSHOU (NGFS) بمحفظة Bitget | NGFS السعر والمخطط البياني | محفظة Bitget] (May 16, 2024)</ref>

<ref name="bscscan-13841">[https://bscscan.com/address/0xe8a11cb7671ebcb9bcaeedad449fe02683b585d6 StandardToken | Address 0xe8a11cb7671ebcb9bcaeedad449fe02683b585d6 | BscScan] (May 16, 2024)</ref>

<ref name="bscscan-13842">[https://bscscan.com/tx/0x8ff764dde572928c353716358e271638fa05af54be69f043df72ad9ad054de25 BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (May 16, 2024)</ref>

<ref name="bscscan-13843">[https://bscscan.com/tx/0xada415135ab3cd4e2784ecbc024fc0500ca3907159023a4dfe6d874f46819eed BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (May 16, 2024)</ref>

<ref name="bscscan-13844">[https://bscscan.com/address/0xa608985f5b40cdf6862bec775207f84280a91e3a NGFSToken | Address 0xa608985f5b40cdf6862bec775207f84280a91e3a | BscScan] (May 16, 2024)</ref>

<ref name="bitqueryexplorer-13845">[https://explorer.bitquery.io/bsc/token/0xe8a11cB7671ebcB9bcAEeDad449FE02683b585d6/smart_contract FENGSHOU (NGFS) Token Smart Contract | Binance (BNB) Smart Chain Mainnet] (May 16, 2024)</ref>

<ref name="listingspy-13846">[https://listingspy.net/token/0xe8a11cb7671ebcb9bcaeedad449fe02683b585d6/ FENGSHOU (NGFS) - SCAM. Do not buy this token!] (May 16, 2024)</ref>

<ref name="coinmarketcap-13847">[https://coinmarketcap.com/dexscan/bsc/0x1ffc9bd669ae782c36b33fcb01f325a28ec3610d/ NGFS/USDT Real-time On-chain PancakeSwap v2 (BSC) DEX Data] (May 16, 2024)</ref></references>

FENGSHOU (NGFS) DelegateCallReserves Attack - Revision history