<?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=KRC_Smart_Contract_Deflationary_Mechanism_Burn_Exploit</id>
	<title>KRC Smart Contract Deflationary Mechanism Burn Exploit - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&amp;feed=atom&amp;title=KRC_Smart_Contract_Deflationary_Mechanism_Burn_Exploit"/>
	<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=KRC_Smart_Contract_Deflationary_Mechanism_Burn_Exploit&amp;action=history"/>
	<updated>2026-05-30T10:03:19Z</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=KRC_Smart_Contract_Deflationary_Mechanism_Burn_Exploit&amp;diff=6863&amp;oldid=prev</id>
		<title>Azoundria: Created page with &quot;{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/krcsmartcontractdeflationarymechanismburnexploit.php}} {{Unattributed Sources}}  Binance Security ImageAn attacker exploited a vulnerability in the KRC smart contract on Binance Smart Chain by bypassing `transfer()` restrictions to burn tokens from the liquidity pair during sell swaps, ultimately profiting $37.1k in USDT through a deflationary mechanism...&quot;</title>
		<link rel="alternate" type="text/html" href="https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=KRC_Smart_Contract_Deflationary_Mechanism_Burn_Exploit&amp;diff=6863&amp;oldid=prev"/>
		<updated>2025-07-31T22:53:23Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{Imported Case Study With About|source=https://www.quadrigainitiative.com/casestudy/krcsmartcontractdeflationarymechanismburnexploit.php}} {{Unattributed Sources}}  &lt;a href=&quot;/cryptocurrencyhackscamfraudwiki/index.php?title=File:Binancesecurity.jpg&quot; title=&quot;File:Binancesecurity.jpg&quot;&gt;thumb|Binance Security Image&lt;/a&gt;An attacker exploited a vulnerability in the KRC smart contract on Binance Smart Chain by bypassing `transfer()` restrictions to burn tokens from the liquidity pair during sell swaps, ultimately profiting $37.1k in USDT through a deflationary mechanism...&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 With About|source=https://www.quadrigainitiative.com/casestudy/krcsmartcontractdeflationarymechanismburnexploit.php}}&lt;br /&gt;
{{Unattributed Sources}}&lt;br /&gt;
&lt;br /&gt;
[[File:Binancesecurity.jpg|thumb|Binance Security Image]]An attacker exploited a vulnerability in the KRC smart contract on Binance Smart Chain by bypassing `transfer()` restrictions to burn tokens from the liquidity pair during sell swaps, ultimately profiting $37.1k in USDT through a deflationary mechanism, with no response or recovery efforts confirmed as of now.&amp;lt;ref name=&amp;quot;tenarmortweet-20825&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;suspicioustransaction1-20826&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;suspicioustransaction2-20827&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;krcexploiter-20828&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;krcexploitcontract-20829&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;krcexploitcontractcreation-20830&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;krctoken-20831&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;krctokencreation-20832&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== About KRC ==&lt;br /&gt;
The KRC smart contract on the Binance Smart Chain was launched on May 22nd.&lt;br /&gt;
&lt;br /&gt;
== The Reality ==&lt;br /&gt;
This sections is included if a case involved deception or information that was unknown at the time. Examples include:&lt;br /&gt;
&lt;br /&gt;
* When the service was actually started (if different than the &amp;quot;official story&amp;quot;).&lt;br /&gt;
* Who actually ran a service and their own personal history.&lt;br /&gt;
* How the service was structured behind the scenes. (For example, there was no &amp;quot;trading bot&amp;quot;.)&lt;br /&gt;
* Details of what audits reported and how vulnerabilities were missed during auditing.&lt;br /&gt;
&lt;br /&gt;
== What Happened ==&lt;br /&gt;
An attacker exploited a vulnerability in the KRC smart contract to burn tokens during sell swaps and gain $37.1k in USDT.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+Key Event Timeline - KRC Smart Contract Deflationary Mechanism Burn Exploit&lt;br /&gt;
!Date&lt;br /&gt;
!Event&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|May 22nd, 2025 7:56:24 AM MDT&lt;br /&gt;
|KRC Token Smart Contract Launched&lt;br /&gt;
|The KRC token smart contract is launched on the Binance Smart Chain.&lt;br /&gt;
|-&lt;br /&gt;
|May 23rd, 2025 4:13:45 PM MDT&lt;br /&gt;
|Malicious Smart Contract Launched&lt;br /&gt;
|The attacker launches a malicious smart contract in preparation for the attack against the KRC token.&lt;br /&gt;
|-&lt;br /&gt;
|May 23rd, 2025 4:18:03 PM MDT&lt;br /&gt;
|First Suspicious Attack Transaction&lt;br /&gt;
|First suspicious attack transaction against the KRC smart contract is exploited on Binance Smart Chain.&lt;br /&gt;
|-&lt;br /&gt;
|May 23rd, 2025 4:19:15 PM MDT&lt;br /&gt;
|Second Suspicious Attack Transaction&lt;br /&gt;
|Second suspicious attack transaction against the KRC smart contract is exploited on Binance Smart Chain.&lt;br /&gt;
|-&lt;br /&gt;
|May 23rd, 2025 8:27:00 PM MDT&lt;br /&gt;
|TenArmor Posts Announcement&lt;br /&gt;
|TenArmor posts an announcement that they have detected the suspicious transaction on the KRC token.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Technical Details ==&lt;br /&gt;
TenArmor reports that the attack reportedly occurred because the attacker was able to bypass the restrictions in the `transfer()` function and burned KRC tokens from the liquidity pair during each sell swap. As a result, they ultimately received more USDT due to the deflationary burning mechanism.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Total Amount Lost ==&lt;br /&gt;
The loss total was reported by TenArmor as $37.1k.&lt;br /&gt;
&lt;br /&gt;
The total amount lost has been estimated at $37,000 USD.&lt;br /&gt;
&lt;br /&gt;
== Immediate Reactions ==&lt;br /&gt;
It's unclear whether or not the project has ever responded to the attack.&lt;br /&gt;
&lt;br /&gt;
== Ultimate Outcome ==&lt;br /&gt;
The incident was reported on by TenArmor.&lt;br /&gt;
&lt;br /&gt;
== Total Amount Recovered ==&lt;br /&gt;
There is no indication that any funds have yet been recovered.&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;
It's unclear if there is any investigation undergoing or potential recovery which may be possible.&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;tenarmortweet-20825&amp;quot;&amp;gt;[https://twitter.com/TenArmorAlert/status/1926102792717980105 TenArmor - &amp;quot;Our system has detected a suspicious attack involving #KRC token on #BSC, resulting in an approximately loss of $37.1 K. It appears that the attacker bypassed the restrictions in the transfer() function and burned KRC  tokens from the pair in every sell swap, finally got more USDT due to the deflationary burning mechanism.&amp;quot; - Twitter/X] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;suspicioustransaction1-20826&amp;quot;&amp;gt;[https://bscscan.com/tx/0xe956390af12b6d8f50e3c7edea6d00e91f54a557605fe040ff9a1bfe5ae90ae2 First Suspicious Transaction Against KRC - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;suspicioustransaction2-20827&amp;quot;&amp;gt;[https://bscscan.com/tx/0x88e1cf17afa0bc81582b42db82ee8e1aa7f58d5dd67a6ed3ad0991c51bae4a81 Second Suspicious Transaction Against KRC - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;krcexploiter-20828&amp;quot;&amp;gt;[https://bscscan.com/address/0x9943f26831f9b468a7fe5ac531c352baab8af655 KRC Exploiter Address - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;krcexploitcontract-20829&amp;quot;&amp;gt;[https://bscscan.com/address/0x0edcff449dc8b13edadfbead841dc8fe522898c9 Malicious Contract By KRC Exploiter - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;krcexploitcontractcreation-20830&amp;quot;&amp;gt;[https://bscscan.com/tx/0xf554946c7410348a1084589bf6f3c62cb46f113fcfc76d6bc380ef3505cfcb2a Malicious Contract Created By KRC Exploiter - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;krctoken-20831&amp;quot;&amp;gt;[https://bscscan.com/address/0xd81f08187e541e94cb5d96efa9a94656ab4080c2 KRC Token Address - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;krctokencreation-20832&amp;quot;&amp;gt;[https://bscscan.com/tx/0xc2a82e7d6fd0bd59587f874b640e70cae5c2c7da9ce7d56e58ef71719ce721fb KRC Token Creation Transaction - BSCScan] (Accessed Jul 31, 2025)&amp;lt;/ref&amp;gt;&amp;lt;/references&amp;gt;&lt;/div&gt;</summary>
		<author><name>Azoundria</name></author>
	</entry>
</feed>