Improper use of `tx.origin`

[dDevAhmed]

• 📚 Overview: Refine and implement: Improper use of tx.origin
• 🎯 Objectives:
  • Implement Implementation needed
  • Add unit tests
  • Verify with protocol invariants
• 🧠 Problem Context: Issue identified during audit: - Impact: Phishing risk.
• 🧩 Technical Scope: Relevant repository module.
• ✅ Acceptance Criteria:
  • Implementation needed is functional
  • Tests passed
  • No regressions
• 🔐 Security / Integrity Considerations: Not specified
• ⏳ Complexity & Effort: Medium
• 🔗 References: Internal Ref #CO-191
• 🏷️ Labels: contracts, stellar-wave, complexity-medium

---

[mansur-codes]

@mansur-codes has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I can easily fix this bug on this issue, please assign, thank you.

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

[a-malik-gh]

@a-malik-gh has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to resolve the issue in view
Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @a-malik-gh to this issue.

[drips-wave]

Congratulations, @a-malik-gh! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @a-malik-gh: 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 🌊