Picky Assist Official Blog

Bug Bounty Program – Bug Beacon

Our Team of dedicated security professionals works vigilantly to keep Picky Assist platform fortified, Even after our scrutinizing if you happen to come across any security issues you may report the same to our security team. We would be honestly thankful for your help and will be more than happy to offer you a reward for submission of security bugs.

We take security issues with absolute seriousness here at Picky Assist !

We provide bug bounties for security related subjects / findings / concerns that are responsibly reported to us. Please read our Rules and Guidelines for bug bounties before you start to hunt.

Majority of the products are either in beta or alpha and rapidly undergoing development and hot fixes so may have functional and UI based bugs however we consider the following category of bugs as serious and offer up to $100 depends on the severity of the bug as listed below;

Qualifying Scope

  1. Remote Code Execution (RCE)
  2. Data Leakage / Theft 
  3. Session Hijacking (Not Stored XSS / Self XSS)
  4. SQL based Injections 
  5. Unauthorized Access to Restricted Area
  6. Server Side Request Forgery
  7. Subdomain/Domain Takeover
  8. Session Fixation
  9. Improper TLS protection
  10. Directory Traversal
  11. Business Logic Issues


Please see which scope included and not included for the bug bounty program

Not Eligible
https://feedbacks.pickyassist.comNot Eligible
http://status.pickyassist.comNot Eligible
https://help.pickyassist.comNot Eligible


If you think you have observed an issue we encourage you to report it to us to [email protected] (in the prescribed mentioned format).

Kindly note our team may not respond if your reporting is not qualified as per our program rules as mentioned in this page

Happy Hunting!!!


  1. Do not attempt attacks against other users during your research.
  2. Don’t violate the privacy of other users, destroy data, disrupt our services, etc.
  3. Do not attempt to gain access to another user’s information or data.
  4. Do not use automated or scanner tools and no DoS or Spam attacks either.
  5. Do not disclose details in public until we patch the issue.
  6. No domains other than https://pickyassist.com, its Facebook App/Mobile App/WAP Site shall be considered or targeted for Security Audits.
  7. Never attempt any non-technical/social attacks against other users or Picky Assist staff.
  8. Bug disclosure communications with Picky Assist Security Team are to remain confidential. Researchers must destroy all artefact created to document vulnerabilities (POC code, videos, screenshots) after the bug report is closed.

What Does Not Qualify?

  1. Bugs that are based on UI/UX or non-functional elements of the product.
  2. Any type of brute force cracking or automated attacks.
  3. Problems that necessitate a significant amount of user interaction and/or social engineering, such as persuading our clients to click on a link provided by an unknown party.
  4. Issues that only affect extensions, plug-ins, or legacy browsers.
  5. Attack vectors that require the use of request interceptor tools or developer tools.
  6. Any issue that has already been reported to us through our bug bounty program.
  7. Vulnerabilities that Picky Assist has determined to be within an acceptable level of operational risk, such as clickjacking.
  8. XSS (or behaviors) that only allow you to attack yourself, such as “Self XSS”. This also includes stored XSS situations where you can’t inject XSS code into other accounts; any self-stored XSS in the same account is not considered for the bug bounty.
  9. Any issues targeting our support, blog, or other third-party sites.
  10. CSV injection.
  11. Session invalidation after password change.
  12. Lack of adherence to best security practices that does not lead to a vulnerability.
  13. Absence of security headers that do not directly result in a vulnerability.
  14. Attacks that require physical access to a user device.
  15. Disclosure of server information or files.
  16. Email spoofing and related best practices.
  17. Missing cookie flags on non-authentication cookies.
  18. Missing best practices in DNS configuration (e.g., DKIM/DMARC/SPF/TXT).
  19. Missing best practices in SSL/TLS configuration.
  20. Missing best practices in Content Security Policy (CSP) or lack of other security-related headers.
  21. Leakage of sensitive tokens (e.g., reset password token) to trusted third parties on a secure connection (HTTPS).
  22. Credential re-usage from public dumps.

The Guidelines to Report Bugs.

  • Report shall be explained sequentially with clear specifications so to reproduce the bug and shall be supported with URL, Videos and Screenshots.
  • Report shall be explained with the impact of bugs in business/ to users.
  • Report shall be submitted with the Reporter’s Name, Email ID and other contact details
  • Report shall be submitted with the details including the Severity and Types of Severity.

Recommended Report Format

At Glance
Provide the information at glance

Severity Index
Critical / High / Medium / Low

Proof Of Concept
Detailed POF with Video or Screencasts

End Points
End points which are affected , if server side or backdoor entries kindly mention the server hostname, IP etc

Steps to Reproduce
Please give step by step to reproduce the bug

Picky Assist Registered Email Address
The account used by you as part of your research

Impact to Users & Business
Explain your findings how this can impact users or our business

Contact Info
Your Name | Email | Profile

Send your report to [email protected] with Subject Contains “Bug Bounty”

Points To Be Noted Before Submitting Report

  1. Please do report the issue with immediate effect.
  2. Please do not upload your findings in any file sharing website/youtube as we prefer you to upload the same in Google Drive/to your private server
  3. Please do try to include only one problem per report to avoid complication.
  4. Please do give a try to reproduce the bug at least thrice before writing a bug report.
  5. Please test the same bug occurrence on other modules of similar description.
  6. Please do read the Bug Report before you submit. 

Please do conclude the report as the point of reporting a bug is to get bugs fixed” 


What is the Picky Assist Bug Beacon Program?

Our Bug Beacon program provides individuals across the world to submit vulnerability reports in prescribed format but no business other than Picky assist will be qualified. All qualified submissions shall be eligible for a payment. Bounties will be paid out at Picky Assist discretion based on the severity and impact of the vulnerability. 

How are bounty payments made?

Bounty payments for accepted issues will be sent out to researchers using bank transfer or Paypal. The amount will vary upon the gravity / severity of the issues reported. 

Will credit be given?

Definitely! Once the issue is patched up, we shall publish the details in the PIcky Assist “Hall of Fame” page. In addition to that we will include the name and link to the researchers responsible for reporting the issue.

Even after submitting an issue I have not received a response!

You will have to provide and we require at least 2-7 days in getting back to you. We do review each report with utmost care and are required to fully understand the scope of all issues reported by you.

Will Picky Assist offer a job for a Security Auditor / for reporting any security related bugs?

We’ve always been proactive in offering jobs to researchers who report any security related bugs but they need to sweep through the HR Interview or Tech Team Interview or both, to prove them more proficient. If they are disinterested in the employment system then they can be offered to work with us as freelance security auditors and we may assign them as and when new versions are updated, whereby you can report a bug and be financially compensated.

What is Picky Assist looking for?

We are looking for any bug maliciously cracking the security of our users, within the purview of our threat model. Finding bigger bugs brings you closer to bigger rewards (maximum $100 being a self funded startup), but all security related bugs shall be bountied.

“We Offer Rewards For Any Security Relevant Bugs. These Comprise Exploits, Vulnerabilities And Any Information About Ongoing Attacks.”

Add comment