Azoundria: Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/evminkbnbscontractremoveliquidityreentrancyattack.php}} {{Unattributed Sources}} EVMInk Logo/HomepageEVMINK has launched a new standard for inscriptions, introducing innovative features for the ecosystem, including native token swaps, on-chain governance, and staking with reward distribution. BNBs were the first to migrate to this new standard, unlocking advanc..."

2025-01-24T22:14:47Z

Created page with "{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/evminkbnbscontractremoveliquidityreentrancyattack.php}} {{Unattributed Sources}} thumb|EVMInk Logo/HomepageEVMINK has launched a new standard for inscriptions, introducing innovative features for the ecosystem, including native token swaps, on-chain governance, and staking with reward distribution. BNBs were the first to migrate to this new standard, unlocking advanc..."

New page

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

[[File:Evmink.jpg|thumb|EVMInk Logo/Homepage]]EVMINK has launched a new standard for inscriptions, introducing innovative features for the ecosystem, including native token swaps, on-chain governance, and staking with reward distribution. BNBs were the first to migrate to this new standard, unlocking advanced features such as wallet integration and cheaper gas fees. However, the platform recently experienced a reentrancy exploit, resulting in a loss of approximately $20,300. The vulnerability, found in the "removeLiquidity" function, allowed an attacker to exploit the system by repeatedly withdrawing BNBs without updating the balance. In response, EVMINK temporarily disabled trading to perform security checks and enhance smart contract security. The platform has covered all user losses and is working on strengthening its infrastructure through additional audits and security measures. Trading will resume once internal verifications are complete, ensuring a more resilient and secure platform for users.<ref name="bscscan-17522" /><ref name="newsletter-17521" /><ref name="tikkalaresearchtwitter-17523" /><ref name="tikkalaresearchtwitter-17524" /><ref name="evm-17525" /><ref name="evminktwitter-17526" /><ref name="evminktwitter-17527" /><ref name="evminktwitter-17528" /><ref name="evminktwitter-17529" /><ref name="evminktwitter-17530" /><ref name="quillauditsaitwitter-17531" /><ref name="lucidsamueltwitter-17532" /><ref name="quillhashgithub-17533" /><ref name="evminktwitter-17534" /><ref name="evminktwitter-17535" /><ref name="0xnicklfranklintwitter-17536" /><ref name="nickfranklin-17537" /><ref name="tenarmoralerttwitter-17538" /><ref name="hermione7812twitter-17539" /><ref name="audit911twitter-17540" />

== About EVM Ink ==
"The communities own indexer Multichain inscription marketplace.Creator launchpad and more."

"We are thrilled to announce the launch of the new standard for inscriptions, marking a transformative milestone for the EVMINK ecosystem.

This update introduces a host of groundbreaking features that elevate how you trade, earn, and interact."

"The New Inscription Token Standard is an enhanced token standard on the EVM blockchain, designed to provide a modular framework of extensions that improve upon the traditional ERC-20 standard."

"- Native Token Swaps: Allows direct token exchanges without relying on decentralized exchanges (DEXs).
- On-Chain Governance: Integrates decentralized governance mechanisms directly into token contracts, allowing for efficient decision-making.
- Staking and Reward Distribution: Enables native staking functionalities with reward mechanisms."

"We’re proud to announce that BNBs will be the first token to migrate to our revolutionary new inscription token standard. As the largest inscription token on @BNBCHAIN by Volume and market cap, BNBs continues to set the benchmark for excellence and innovation.

This migration marks a new chapter for all inscriptions as BNBs will take the lead, unlocking advanced features like wallet integration, swapping, liquidity pools, and cheaper gas fees under the new standard. The future of inscriptions is here, and it starts with BNBs leading the charge!"

== The Reality ==
"In removeLiquidity() function, token transfer should happen before ETH transfer because token balance is used to calculate amountNative and amountToken to remove."

== What Happened ==
"A suspicious reentrancy attack involving bnbs (bnbs) occurred on the BSC chain, resulting in a loss of approximately $20,300."
{| class="wikitable"
|+Key Event Timeline - EVMInk BNBS Contract Remove Liquidity Reentrancy Attack
!Date
!Event
!Description
|-
|December 9th, 2024 3:14:00 AM MST
|New Token Inscription Standard
|EVMInk announces a new token inscription standard on their website.
|-
|December 10th, 2024 4:09:00 AM MST
|Launch Announces As Success
|EVMInk highlightes the success of their new launch, with notable statistics including $160K+ in daily trading volume, 550+ users migrated to new Token Standard, $50K+ locked in liquidity, and 1,500 transactions.
|-
|December 11th, 2024 12:58:00 AM MST
|Thrilled With Audit Announcement
|"We’re thrilled to announce that BNBs’s smart contract has been audited and verified, solidifying our commitment to security with zero compromises."
|-
|December 11th, 2024 5:45:21 PM MST
|Binance Smart Chain Transaction
|The malicious transaction which is reported by SlowMist.
|-
|December 11th, 2024 7:11:00 PM MST
|TenArmor Transaction Analysis
|The TenArmor team posts an initial analysis of the exploit and
|-
|December 11th, 2024 7:28:00 PM MST
|Huge Gas Fees Analysis Underway
|"Our team is currently fixing some bugs on the huge gas fee involved, and modify the issue happens on UI side. Please DO NOT do any transactions / activity until further notice. Everyone's assets are secured and safe."
|-
|December 11th, 2024 7:33:00 PM MST
|Hermione7812 Reply To TenArmor Analysis
|Hermione7812 responds to the initial TenArmor tweet with additional information about the vulnerability. "In removeLiquidity() function, token transfer should happen before ETH transfer because token balance is used to calculate amountNative and amountToken to remove."
|-
|December 12th, 2024 12:19:00 AM MST
|Issue Unfortunately Announcement
|The EVMInk team posts an announcement that there has been an issue. They are working with their audit partner Quill Audits towards a resolution.
|-
|December 12th, 2024 12:41:00 AM MST
|Quill Audits Announcing Postmortem
|Quill Audits announces that they are conducting a post-mortem and will be sharing their results with the team shortly.
|-
|December 12th, 2024 7:29:00 AM MST
|Audit911 Analysis Posted
|Audit911 posts an analysis of the exploit on Twitter/X. Their AI detection program reportedly found the vulnerability.
|-
|December 12th, 2024 12:11:00 PM MST
|Tikkala Research Analysis
|Tikkala Research posts an announcement of the vulnerability, reporting this as a "classical re-entry bug". They edit moments later to add the transaction link.
|-
|December 12th, 2024 12:55:00 PM MST
|Tikkala Research Analysis
|Tikkala Research posts a more detailed analysis,
|-
|December 17th, 2024 2:46:00 AM MST
|Nick L Franklin Analysis
|Nick L Franklin posts a technical analysis of the exploit with additional details, which references a post on his website.
|-
|December 19th, 2024 3:38:00 AM MST
|Downtime For Security Check
|The platform announces downtime in order to perform a security check.
|-
|January 11th, 2025 4:09:00 AM MST
|Working Through Towards Relaunch
|The platform posts an update that they are siligently working through security checks and plan to relaunch shortly.
|}

== Technical Details ==
"A classical re-entry bug hit one of the @evmink new BNBS contract which leads ~20k lost. Attacker has been labeled as "FEGtoken Exploiter"."

"root cause is the balance update after the re-entry which impacts the K value. Later on a small amount of bnbs token could swap out almost all BNB in the victim account."

"bnbs token exploit. Root cause of bnbs exploit is reentrance. "removeLiquidity" function has no reentrance check, and bnbs balance is updated after eth sent, this can be used for reentrance attack. As you can see, "removeLiquidity" function is called in fallback function, and in each "removeLiquidity" function, he gets more and more bnbs tokens, as bnbs balance is not updated. After that, he exchanged all bnbs tokens to WBNB, total loss is about $20k."

== Total Amount Lost ==
The total amount lost has been estimated at $20,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 ==
"Our team is currently fixing some bugs on the huge gas fee involved, and modify the issue happens on UI side.

Please DO NOT do any transactions / activity until further notice. Everyone's assets are secured and safe."

"there’s been an issue unfortunately, and our team is actively working to resolve it. alongside our audit partners, @quillaudits_ai. user funds remain safe and secured. we’ll provide more updates shortly—thank you for your patience as we ensure everything is back on track."

Audit911 reports that their "team detected today that the bnbs project was hacked and the funds lost were ~20ku. Our AI detection system can already identify this vulnerability"

"A suspicious reentrancy attack involving bnbs (bnbs) occurred on the BSC chain, resulting in a loss of approximately $20,300."

== 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 ==
Protocol has promised to cover all user assets.

There do not appear to have been any funds recovered in this case.

== Ongoing Developments ==
"We have scheduled temporarily disable EVMINK platform to facilitate the final phase of internal security checks, ensuring a smooth and comprehensive process. This follows the completion of a rigorous security audit and reflects our commitment to maintaining the highest levels of safety and reliability for our users.

Please note:
- All user funds remain secure, the liquidity pools are fully operational.
- Once the platform is reactivated, tokens will be reallocated and issued promptly to all eligible users.

In the background, we are also preparing additional features aligned with the new token standard and working closely with the community to refine and enhance the ecosystem.

We appreciate your patience and support as we prioritize the security and performance of our platform. Updates will be provided through our official channels.

Thank you for your trust, All funds are SAFE."

"Trading is temporarily halted, We are investigating the issues with liquidity pool"

"Over the past few weeks, we have been diligently reinforcing the security of our platform after identifying a vulnerability in our smart contract, which led to an on-chain attack resulting in a $20.3K loss. While this was an unexpected setback, it has provided us with an opportunity to strengthen our security framework and ensure a more resilient platform moving forward."

"User funds remain fully protected – EVMINK has covered the entire loss from our reserves, ensuring that no user assets are affected. Reinforced smart contract security – Additional audits and advanced security measures have been implemented to prevent similar exploits. Comprehensive system improvements – Beyond just fixing the issue, we have enhanced the entire infrastructure to make the platform stronger and more efficient."

"We are approaching the final stage of internal security verification. Over the next few days, we will be announcing a strategic launch date for the platform, ensuring that we go live with maximum confidence and stability.

This is more than just a relaunch—it’s a major step forward. The lessons learned have allowed us to build an even stronger foundation, and we are excited for what’s ahead. Thank you for your patience, trust, and support as we prepare for a new and improved EVMINK."
== 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="bscscan-17522">[https://bscscan.com/tx/0x33c70f2aaf54960dc96b440061b9354fb40ef477b54755b79332f707d82909cc BNB Smart Chain Transaction Hash (Txhash) Details | BscScan] (Accessed Jan 24, 2025)</ref>

<ref name="newsletter-17521">[https://newsletter.blockthreat.io/p/blockthreat-week-50-2024 BlockThreat - Week 50, 2024] (Accessed Jan 24, 2025)</ref>

<ref name="tikkalaresearchtwitter-17523">[https://twitter.com/TikkalaResearch/status/1867286243245273505 @TikkalaResearch Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="tikkalaresearchtwitter-17524">[https://twitter.com/TikkalaResearch/status/1867286063401906229 @TikkalaResearch Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evm-17525">[https://evm.ink/?token=0xf5817927593c47ddabf78344ba43dacf43cd73e6&networkId=56 Inscriptions] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17526">[https://twitter.com/evmink/status/1866063979413655748 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17527">[https://twitter.com/evmink/status/1866075427284070839 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17528">[https://twitter.com/evmink/status/1866440005025202221 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17529">[https://twitter.com/evmink/status/1866754388049662110 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17530">[https://twitter.com/evmink/status/1867033753413152971 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="quillauditsaitwitter-17531">[https://twitter.com/quillaudits_ai/status/1867112552628465982 @quillaudits_ai Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="lucidsamueltwitter-17532">[https://twitter.com/LucidSamuel_/status/1867111454190739832 @LucidSamuel_ Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="quillhashgithub-17533">[https://github.com/Quillhash/QuillAudit_Reports/blob/master/EVM.INK%20Smart%20Contract%20Audit%20Report%20-%20QuillAudits.pdf QuillAudit_Reports/EVM.INK Smart Contract Audit Report - QuillAudits.pdf at master · Quillhash/QuillAudit_Reports · GitHub] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17534">[https://twitter.com/evmink/status/1869693811687117186 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="evminktwitter-17535">[https://twitter.com/evmink/status/1878036486081400867 @evmink Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="0xnicklfranklintwitter-17536">[https://twitter.com/0xNickLFranklin/status/1868955959777017941 @0xNickLFranklin Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="nickfranklin-17537">[https://nickfranklin.site/2024/12/17/bnbs-token-exploit/ bnbs token exploit. – Defi hack analysis] (Accessed Jan 24, 2025)</ref>

<ref name="tenarmoralerttwitter-17538">[https://twitter.com/TenArmorAlert/status/1867029448014315893 @TenArmorAlert Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="hermione7812twitter-17539">[https://twitter.com/Hermione7812/status/1867034960089030729 @Hermione7812 Twitter] (Accessed Jan 24, 2025)</ref>

<ref name="audit911twitter-17540">[https://twitter.com/audit_911/status/1867215299059294318 @audit_911 Twitter] (Accessed Jan 24, 2025)</ref></references>

EVMInk BNBS Contract Remove Liquidity Reentrancy Attack - Revision history