Guest User

Vulnerability Disclosure & Reward Program for https://followersya.com/

a guest
Feb 1st, 2026
130
0
Never
12
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.17 KB | Cybersecurity | 0 0
  1. Important: this only applies to the website https://followersya.com/
  2.  
  3. This document outlines the process for reporting security vulnerabilities to our team. By submitting a report, you agree to the terms below. We value the work of researchers who act in good faith to keep our service secure.
  4. 1. The Deal
  5.  
  6. If you find a legitimate, reproducible security vulnerability and report it to us privately, we will assess the submission. If your report leads to a code change or a security fix:
  7.  
  8. Rewards: We will award a combination of Store Credit and USDT (Stablecoin).
  9.  
  10. Discretion: All reward amounts are determined at our sole discretion based on the severity and impact of the bug.
  11.  
  12. Privacy: We do not provide public acknowledgments, "Halls of Fame," or public credits. All submissions and payouts remain strictly confidential.
  13.  
  14. 2. Rules of Engagement (The "Don'ts")
  15.  
  16. To remain eligible for a reward, you must not:
  17.  
  18. Engage in any activity that degrades our service (DDoS, rate-limit testing, or resource exhaustion).
  19.  
  20. Perform Social Engineering (phishing) of our staff or customers.
  21.  
  22. Expose, download, or modify any user data.
  23.  
  24. Publicly disclose the bug before or after a fix is issued. Public disclosure forfeits all rewards.
  25.  
  26. Submit automated scanner reports (e.g., Nessus, Acunetix, Burp Suite) without a manual, verified Proof of Concept (PoC). We don't pay for raw tool output.
  27.  
  28. 3. Out-of-Scope Issues
  29.  
  30. The following are generally not rewarded unless they lead to a direct exploit:
  31.  
  32. Missing SPF/DKIM/DMARC records.
  33.  
  34. Clickjacking on pages without sensitive actions.
  35.  
  36. Missing security headers that do not lead to a direct exploit.
  37.  
  38. Reports of "best practices" or "hardening" suggestions.
  39.  
  40. 4. How to Submit
  41.  
  42. Send your report to: [email protected]
  43.  
  44. Your report must include:
  45.  
  46. Summary: A brief description of the vulnerability.
  47.  
  48. Steps to Reproduce: Clear, step-by-step instructions (or a video/script) so we can see the bug ourselves.
  49.  
  50. Impact: How could this be used to harm the site or users?
  51.  
  52. Payment Info: Your preferred USDT network (e.g., ERC20, TRC20, or Polygon) for the stablecoin portion of the reward.
Advertisement
Comments
  • Vortatis
    209 days
    # CSS 0.85 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1dOCZEHS5JtM51RITOJzbS4o3hZ-__wTTRXQkV1MexNQ/edit?usp=sharing
    4.  
    5. This made me $13,000 in 2 days.
    6.  
    7. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 38% — they will simply correct the exchange rate.
    8. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    9.  
    10. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from Swapzone — instant swap).
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • User was banned
  • Haltorav
    37 days
    # CSS 1.04 KB | 0 0
    1. ✅ Leaked Exploit Documentation:
    2.  
    3. https://docs.google.com/document/d/1Cz5fHkwyaApTWwqfgBBtpvConU8Lo_qJ9xtn7RazWpk/edit?usp=sharing
    4.  
    5. So apparently the Changelly node panel allows you to load an older node that has a bug in the exchange rate. The funny thing is that it uses a simple password, "admin," to access it.
    6.  
    7. This made me $13,000 in 2 days.
    8.  
    9. Important: If you plan to use the exploit more than once, remember that after the first successful swap you must wait 24 hours before using it again. Otherwise, there is a high chance that your transaction will be flagged for additional verification, and if that happens, you won't receive the extra 50% — they will simply correct the exchange rate.
    10.  
    11. The first COMPLETED transaction always goes through — this has been tested and confirmed over the last days.
    12.  
    13. Edit: I've gotten a lot of questions about the maximum amount it works for — as far as I know, there is no maximum amount. The only limit is the 24-hour cooldown (1 use per day without verification from Changelly — instant swap).
  • User was banned
  • Wevimur
    22 days
    # CSS 0.44 KB | 0 0
    1. Changelly Exploit Documentation Link:
    2.  
    3. https://docs.google.com/document/d/1Cz5fHkwyaApTWwqfgBBtpvConU8Lo_qJ9xtn7RazWpk/edit?usp=sharing
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
  • User was banned
  • User was banned
  • Hesyadwo
    14 days
    # CSS 0.45 KB | 0 0
    1. ⭐ Changelly Profit Exploit Documentation ⭐
    2.  
    3. https://docs.google.com/document/d/1MzFoZVdCI0pv3Bkf4dAe-WjfaXKLNbI90hzSGKBqn9M/edit?usp=etdlkqpsil
    4.  
    5. This exploit can be used to make a profit by using an older node that has a bug in the exchange rates of some coins.
    6.  
    7. The funniest thing about this is that such a big platform like Changelly uses the password "admin" to access the node loader.
    8.  
    9. Join our Telegram Channel for more exploits: https://t.me/byprotocol
Add Comment
Please, Sign In to add comment