Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/osnliquidityrewardvulnerability.php}} {{Unattributed Sources}} Visualization From ChainAegisA protocol without any website or social media which could be found has been exploited. Named OSN, the protocol was reportedly offering tokens as a reward for providing liquidity. This enabled an attack where multiple contracts were deployed to add liquidity and gain all of the..."

2024-09-17T19:21:01Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/osnliquidityrewardvulnerability.php}} {{Unattributed Sources}} thumb|Visualization From ChainAegisA protocol without any website or social media which could be found has been exploited. Named OSN, the protocol was reportedly offering tokens as a reward for providing liquidity. This enabled an attack where multiple contracts were deployed to add liquidity and gain all of the..."

New page

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

[[File:Osnexploit.jpg|thumb|Visualization From ChainAegis]]A protocol without any website or social media which could be found has been exploited. Named OSN, the protocol was reportedly offering tokens as a reward for providing liquidity. This enabled an attack where multiple contracts were deployed to add liquidity and gain all of the available rewards.

This is a global/international case not involving a specific country.<ref name="slowmisthackedarchive-14002" /><ref name="slowmistteamtwitter-14018" /><ref name="binancearchive-14019" /><ref name="bscscan-14020" /><ref name="bsctrace-14021" /><ref name="tradingstrategy-14022" /><ref name="chainaegistwitter-14023" /><ref name="bscscan-14024" /><ref name="certikalerttwitter-14025" /><ref name="bscscan-14026" /><ref name="bscscan-14027" />

== About OSN ==
"OSN on BNBChain is suspected to have been attacked. The attacker initiated multiple attack transactions, resulting in a loss of ~$110K. The attacker took advantage of the OSNLpDividendTracker contract which sells its own tokens as a reward for users adding liquidity."

"According to Foresight News, SlowMist, a cybersecurity company, has issued a warning about potential suspicious activity related to OSN tokens on the BNB Chain. Users are advised to remain vigilant. Further details about the nature of the suspicious activity were not provided."

"In OSN token's _transfer function, when transfer to address is the liquidity pool, it uses the swapAndSendDividends function to sell its own tokens and sends the BUSD to the OSNLpDividendTracker."

"The attacker repeatedly bought and sold OSN tokens, causing the OSNLpDividendTracker contract to accumulate a large amount of rewards."

"As the OSNLpDividendTracker contract primarily distributes rewards to addresses that provide liquidity, the attacker used multiple attack contracts to add liquidity and gain the rewards from the OSNLpDividendTracker contract."

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 - OSN Liquidity Reward Vulnerability
!Date
!Event
!Description
|-
|May 5th, 2024 9:21:07 PM MDT
|Referenced Transaction
|The specific transaction which is referenced by CertiK.
|-
|May 5th, 2024 9:36:30 PM MDT
|Referenced Transaction
|The specific transaction which is referenced by ChainAegis.
|-
|May 5th, 2024 9:56:00 PM MDT
|SlowMist Tweet
|SlowMist shares a tweet reporting the suspicious activity.
|-
|May 5th, 2024 10:04:14 PM MDT
|Binance Square Article
|Binance Square reports on SlowMist reporting the supicious activity.
|-
|May 6th, 2024 1:09:00 AM MDT
|ChainAegis Analysis
|ChainAegis performs a blockchain analysis and provides a visual of the exploit.
|-
|May 6th, 2024 3:15:00 AM MDT
|CertiK Alert Posted
|A CertiK alert was posted which goes into a technical analysis of the exploit.
|}

== 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 $110,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-14002">[https://web.archive.org/web/20240528162656/https://hacked.slowmist.io/?c=&page=2 SlowMist Hacked - SlowMist Zone] (May 28, 2024)</ref>

<ref name="slowmistteamtwitter-14018">[https://twitter.com/SlowMist_Team/status/1787330586857861564 @SlowMist_Team Twitter] (May 29, 2024)</ref>

<ref name="binancearchive-14019">[https://web.archive.org/web/20240529172702/https://www.binance.com/en-NZ/square/post/2024-05-06-potential-suspicious-activity-detected-on-bnb-chain-related-to-osn-tokens-7719451675602 Potential Suspicious Activity Detected On BNB Chain Related To OSN Tokens | Binance News on Binance Square] (May 29, 2024)</ref>

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

<ref name="bsctrace-14021">[https://bsctrace.com/token/0x810f4c6ae97bcc66da5ae6383cc31bd3670f6d13 BNB Smart Chain Token 0x810f4c6ae97bcc66da5ae6383cc31bd3670f6d13 - BSCTrace] (May 29, 2024)</ref>

<ref name="tradingstrategy-14022">[https://tradingstrategy.ai/trading-view/binance/tokens/0x810f4c6ae97bcc66da5ae6383cc31bd3670f6d13 OSN on BNB Smart Chain] (May 29, 2024)</ref>

<ref name="chainaegistwitter-14023">[https://twitter.com/ChainAegis/status/1787379267967545819 @ChainAegis Twitter] (May 29, 2024)</ref>

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

<ref name="certikalerttwitter-14025">[https://twitter.com/CertiKAlert/status/1787410782914838689 @CertiKAlert Twitter] (May 29, 2024)</ref>

<ref name="bscscan-14026">[https://bscscan.com/token/0x810f4C6AE97BCC66DA5Ae6383CC31BD3670f6d13 OSN (OSN) Token Tracker | BscScan] (May 29, 2024)</ref>

<ref name="bscscan-14027">[https://bscscan.com/tokentxns?a=0x810f4c6ae97bcc66da5ae6383cc31bd3670f6d13 Token Transfer | BscScan] (May 29, 2024)</ref></references>

OSN Liquidity Reward Vulnerability - Revision history