security: Chainalysis API key exposed via window global

[nanaf6203-bit]

Summary

src/utils/security/blockchainSecurity.ts reads (window as any).__CHAINALYSIS_API_KEY__ from global window, making the key trivially extractable from the bundle / runtime.

Affected area

src/utils/security/blockchainSecurity.ts end of file

Steps to reproduce / impact

Browser users can extract API keys via DevTools, exposing third-party services to quota theft and abuse.

Expected behaviour

Move API keys to a Next.js API route that proxies requests; the browser should never see the key. If a key is unavoidable, restrict by domain and rotate regularly.

Acceptance criteria

• Provide an /api/security/address-check proxy.
• Browser code calls the proxy only.
• Add CI grep that fails if a hardcoded __ global is shipped.

[koder-ns]

@koder-ns has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hi, I am a good develper with problem solving and debugging skills. and an enthusiastic when it comes to open source. i would like to address this issue if assigned thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @koder-ns to this issue.

[fredericklamar342-prog]

@fredericklamar342-prog has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Kindly assign to me please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @fredericklamar342-prog to this issue.

[Dev-ElvisTobi]

@BigElv has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I would love to work on this issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigElv to this issue.

[danieloche635-bit]

@danieloche635-bit has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would like to work on this issue sir you can trust me with the work

ℹ️ Repo Maintainers: To accept this application, review their application or assign @danieloche635-bit to this issue.

[drips-wave]

Congratulations, @danieloche635-bit! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @danieloche635-bit: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @danieloche635-bit as part of the Stellar Wave Program's 6th Wave 🥳

😎 @danieloche635-bit: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.