https://immunefi.com/bounty/tonic/
https://immunefi.com/bounty/burrow/
https://immunefi.com/bounty/octopusnetwork/

https://twitter.com/auroraisnear/status/1682372465379643392?s=46&t=w1K-2akWm132Lj7mGi5p2g

https://near-genesis.gitbook.io/introduction/near-genesis/audits

https://github.com/HalbornSecurity/PublicReports/blob/master/NEAR%20Smart%20Contract%20Audits/MetaPool_Katherine_Fundraising_and_Bond_Market_NEAR_Smart_Contract_Security_Audit_Report_Halborn_Final%20.pdf

https://blog.metapool.app/2023/06/21/halborns-audit-ensures-robust-security-for-the-meta-pool-protocol/

Garvit | Electron
Posting this thread to address the security concerns raised on Electron Bridge.

1/3
Yes, we are aware of the issue, and we had taken necessary precautions to mitigate this before the launch of the bridge itself. This vulnerability is not exploitable on the bridge right now.

https://twitter.com/garvitgoel03/status/1670351793870761985?s=46&t=w1K-2akWm132Lj7mGi5p2g

Maksym Zavershynskyi (nearmax.near) ⋈
@weikengchen @nearprotocol @labs_electron That's why @NEARDevHub is looking to publicly audit these circuits and determine the next course of actions https://t.co/dhh6K0r4Qw . To clarify, @wormholecrypto 's NEAR<>ETH ZK bridge is based on entirely different circuits developed by @ZpokenWeb3 .

https://twitter.com/mzavershynskyi/status/1670197415994101760?s=46&t=w1K-2akWm132Lj7mGi5p2g

Weikeng Chen
"Electron Labs' bridge between NEAR and Ethereum is vulnerable. Zk circuits used for the NEAR light client are incomplete and severely under-constrained. It is possible to create valid proofs for invalid set of signatures. User funds are at risk!" @nearprotocol? @labs_electron?

https://twitter.com/weikengchen/status/1670163273759735808?s=46&t=w1K-2akWm132Lj7mGi5p2g

https://twitter.com/rahul__ghangas/status/1666366824395739136?s=46&t=w1K-2akWm132Lj7mGi5p2g

https://docs.veax.com/overview/security/external-smart-contract-audits/

StaderLabs - NEARx
Staking Reaudit
NEAR Smart Contract Security
Audit
Prepared by: Halborn
Date of Engagement: August 29th, 2022 - September 14th, 2022

https://www.staderlabs.com/docs/near/StaderLabs%20NearX%20Staking%20Smart%20Contract%20Final%20Reaudit%20by%20Halborn.pdf

https://www.halborn.com/blog/post/stader-labs-nearx-update

Find original audit before exploit

example and reference in readme instead of putting in main readme as PR Best Pracice

Contribution Guidelines

We welcome all types of contributions to our project, including but not limited to:

• Suggesting new reference techniques which prioritize smart contract vulnerability detection.
• Adding exploits or slips up and firms that slipped up with reference to their initial audit
• Adding active or (marking old bug programs as deactive)
• Adding additional audits (make sure to reference original audit in table but also upload the pdf of the audit to the Audit folder with the following naming convention YEAR-MONTH-DAY-FIRM-SCOPE-OF-AUDIT.pdf
  Adding additional security firms (note only add the firm from now on if you have also provided an audit firm in the same PR
  Fixing typos and streamlining the categorization process
• Adding additional NEAR Security resources
  -Add more projects that you are asking for audits to
• End to End testing and Appsec reports
  Suggesting improvements to the classification standard
  Correcting mislabeled bug and exploits or descrbing an audit more cleary (For ex; HERE Wallet -> HERE Wallet liquid staking)
• Improvements to contribution guidelines

Format

• Make a PR and make sure to # the close the issue number if relevant

Thank you for your contributions!

https://arweave.net/WvB-T_sg6HbpG08NLutna0bw65hq4tkZZoUJzw4iRK4

March 29, 2023, MB-Contract, Mintbase by Ottersec

https://github.com/NEARFoundation/near-sdk-contract-tools/blob/develop/documents/NEAR%20Contract%20Tools%20-%20Final%20-%2005.05.2023.pdf

May 5, 2023

https://aurora.dev/audits

with naming convention
year-month-day-firmname-nameofcontractedit.pdf

add this to readme

https://chubk.com/ref-finance-hacked-for-nearly-3-million-dollars-and-plans-to-compensate-users/

NEAR IBC from Octopus just went through a formal auditing. https://github.com/octopus-network/near-ibc/blob/main/auditing/blocksec_near-ibc_v1.0_signed.pdf

September 18, 2023
Blocksec

https://github.com/nameskyteam/assets/blob/113e1251c10692ca50023871449844b4d8cfcffd/NameSky%20Security%20Analysis%20by%20Pessimistic.pdf