Infosec Institute

Open Bug Bounty mentioned in the
Top 6 Bug Bounty programs of
2022 by the InfoSec Institute

The Hacker News

Open Bug Bounty named among the
Top 5 Bug Bounty programs of 2021
by The Hacker News

For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,775,119 coordinated disclosures
1,467,786 fixed vulnerabilities
2,089 bug bounty programs, 4,024 websites
56,752 researchers, 1,734 honor badges

Lapak Maboy Bug Bounty Program

Lapak Maboy runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of Lapak Maboy

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between Lapak Maboy and researchers.

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

*.pgpmail.lapakmaboy.com
mta-sts.lapakmaboy.com
cloud.lapakmaboy.com

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

To ensure that your vulnerability report is considered, please provide clear and detailed instructions on how to reproduce the issue. Additionally, include an attack scenario that describes how the vulnerability can be exploited, along with an assessment of its potential security impact. Accurate information is crucial for evaluating and addressing the report.

- You must comply with the security policy outlined in our Security Policy.
- Include screenshots or screen recordings to clarify your report.
- Provide a brief remediation guide to help us address the vulnerability.
- Ensure the report is submitted confidentially to protect the information.
- If possible, submit files in an encrypted format (e.g., using PGP/GPG) to enhance data security.

Your contribution is invaluable in maintaining the security and integrity of our system. Each report submitted in accordance with the above requirements will be thoroughly reviewed and given full attention by our security team.

Testing Requirements:

We appreciate your participation in our bug bounty program. However, to ensure the security and stability of our system, please adhere to the following testing requirements:

- Do not perform DDoS (Distributed Denial of Service) attacks or any actions that could overload or damage our servers.
- Do not use social engineering techniques to gain access to or obtain sensitive information.
- Do not engage in any activities that could exacerbate server performance or our network infrastructure, including but not limited to excessive exploitation or intensive testing without prior approval.

By complying with these requirements, you help us maintain the integrity and security of our system while allowing us to effectively address any vulnerabilities found.

Possible Awards:

We greatly appreciate your contributions in reporting vulnerabilities to improve the security of our systems. As a token of our appreciation, we offer the following possible rewards for researchers who provide valid and valuable reports:

- Recommendation in the researcher’s profile.
- Mention and display on our hall of fame page.
- Certificate of appreciation for your contribution.
- Opportunity to collaborate further on security projects with us.

We would also like to inform you that, as Lapak Maboy is a small micro business and does not have any sponsors, our bug bounty program does not offer monetary or material rewards. Nevertheless, we hope that the non-material recognition we offer serves as meaningful appreciation for your contributions.

Special Notes:

- Reports must be submitted confidentially and must not be disclosed to any third party without prior written consent from us.
- You must not publicly disclose any information related to the vulnerability until it has been resolved and we have given explicit permission to do so.
- All interactions and communications regarding the vulnerability must be conducted in a confidential manner.
- Ensure that all data related to the vulnerability is handled securely and encrypted where possible.
- Do not access, modify, or delete any data that does not belong to you during your testing.
- Testing should be limited to your own accounts and devices, and should not impact the operation of the system for other users.
- Avoid any actions that could lead to a data breach, unauthorized data access, or violate user privacy.
- Do not share any findings on social media, blogs, or any other public platforms without our consent.
- All testing activities must comply with relevant laws and regulations.
- Provide all findings in a detailed and clear manner to aid in the resolution process.

By adhering to these special notes, you help us ensure that the bug bounty program is conducted in a responsible and secure manner, fostering a collaborative effort to improve the security of our system.

Other Submissions Handling

Website owner want to receive information about other vulnerabilities

Notifications:

[email protected]

PGP Key:

Show key

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEZ26TlRYJKwYBBAHaRw8BAQdAUpRjnF+EELhS9JSwn7rhxeJAShkOt07tPwmQ
23ppj2m0PlNlY3VyaXR5IFBHUG1haWwgTGFwYWsgTWFib3kgPHNlY3VyaXR5QHBn
cG1haWwubGFwYWttYWJveS5jb20+iJMEExYKADsWIQRViuIIfWHbv53BTXpyZOxr
aw2DMwUCZ26TlQIbAwULCQgHAgIiAgYVCgkICwIEFgIDAQIeBwIXgAAKCRByZOxr
aw2DM21tAQCKeqKQcg8FuxZx8ohQD7MRojWmKu2mGUi7XW6C/l8ImAEAgdeG03NW
fUAzeGQ/6TvjJIzXsSOCwZvJTZBmUXJ9uQ64OARnbpOVEgorBgEEAZdVAQUBAQdA
nIOyCYQGDFyfo54ULExOJ5Ws/Gk2m0u+/3L1JiDaQDcDAQgHiHgEGBYKACAWIQRV
iuIIfWHbv53BTXpyZOxraw2DMwUCZ26TlQIbDAAKCRByZOxraw2DM3frAQCenTIy
OMw998w9R0tTDOkEhq+dPS6JMXis2FIYIorO9wD+PNxND6zYKMGXsIf6G4PSPC3X
vCeLzKdJsS4LsE7uYAo=
=VzLG
-----END PGP PUBLIC KEY BLOCK-----

General Requirements:

To ensure that your vulnerability report is considered, please provide clear and detailed instructions on how to reproduce the issue. Additionally, include an attack scenario that describes how the vulnerability can be exploited, along with an assessment of its potential security impact. Accurate information is crucial for evaluating and addressing the report.

- You must comply with the security policy outlined in our Security Policy.
- Include screenshots or screen recordings to clarify your report.
- Provide a brief remediation guide to help us address the vulnerability.
- Ensure the report is submitted confidentially to protect the information.
- If possible, submit files in an encrypted format (e.g., using PGP/GPG) to enhance data security.

Your contribution is invaluable in maintaining the security and integrity of our system. Each report submitted in accordance with the above requirements will be thoroughly reviewed and given full attention by our security team.

Testing Requirements:

We appreciate your participation in our bug bounty program. However, to ensure the security and stability of our system, please adhere to the following testing requirements:

- Do not perform DDoS (Distributed Denial of Service) attacks or any actions that could overload or damage our servers.
- Do not use social engineering techniques to gain access to or obtain sensitive information.
- Do not engage in any activities that could exacerbate server performance or our network infrastructure, including but not limited to excessive exploitation or intensive testing without prior approval.

By complying with these requirements, you help us maintain the integrity and security of our system while allowing us to effectively address any vulnerabilities found.

Possible Awards:

We greatly appreciate your contributions in reporting vulnerabilities to improve the security of our systems. As a token of our appreciation, we offer the following possible rewards for researchers who provide valid and valuable reports:

- Recommendation in the researcher’s profile.
- Mention and display on our hall of fame page.
- Certificate of appreciation for your contribution.
- Opportunity to collaborate further on security projects with us.

We would also like to inform you that, as Lapak Maboy is a small micro business and does not have any sponsors, our bug bounty program does not offer monetary or material rewards. Nevertheless, we hope that the non-material recognition we offer serves as meaningful appreciation for your contributions.

Special Notes:

- Reports must be submitted confidentially and must not be disclosed to any third party without prior written consent from us.
- You must not publicly disclose any information related to the vulnerability until it has been resolved and we have given explicit permission to do so.
- All interactions and communications regarding the vulnerability must be conducted in a confidential manner.
- Ensure that all data related to the vulnerability is handled securely and encrypted where possible.
- Do not access, modify, or delete any data that does not belong to you during your testing.
- Testing should be limited to your own accounts and devices, and should not impact the operation of the system for other users.
- Avoid any actions that could lead to a data breach, unauthorized data access, or violate user privacy.
- Do not share any findings on social media, blogs, or any other public platforms without our consent.
- All testing activities must comply with relevant laws and regulations.
- Provide all findings in a detailed and clear manner to aid in the resolution process.

By adhering to these special notes, you help us ensure that the bug bounty program is conducted in a responsible and secure manner, fostering a collaborative effort to improve the security of our system.

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  Information How quickly researchers get responses to their submissions.
Remediation Time  Information How quickly reported submissions are fixed.
Cooperation and Respect  Information How fairly and respectfully researchers are being treated.

Researcher's comments

No comments so far.

  Latest Patched

 22.01.2025 mylegacy.life.gov.sg
 22.01.2025 fics.nust.edu.pk
 21.01.2025 officemarket.am
 20.01.2025 public.tameside.gov.uk
 20.01.2025 hp.com
 20.01.2025 ted.europa.eu
 19.01.2025 serraria.pb.gov.br
 17.01.2025 cmpentecoste.ce.gov.br

  Latest Blog Posts

04.12.2023 by BAx99x
Unmasking the Power of Cross-Site Scripting (XSS): Types, Exploitation, Detection, and Tools
04.12.2023 by a13h1_
$1120: ATO Bug in Twitter’s
04.12.2023 by ClumsyLulz
How I found a Zero Day in W3 Schools
04.12.2023 by 24bkdoor
Hack the Web like a Pirate: Identifying Vulnerabilities with Style
04.12.2023 by 24bkdoor
Navigating the Bounty Seas with Open Bug Bounty

  Recent Recommendations

    13 January, 2025
    nzpdev:
Andrea discovered an XSS vulnerability on one of our pages. We promptly patched that thanks to her report. We give top marks for spotting our mistake. Thank you again
    20 December, 2024
    CygnusEd:
Thank you very much for your reporting a XSS vulnerability on my site.
Thanks also for the friendly communication!
Great job!
    10 December, 2024
    Sim:
Thank you for identifying an old development project. Information provided was clear allowing a swift removal of the offending code.
    10 December, 2024
    privacysafe:
Andrea is very professional and reported an issue responsibly and in a timely manner, with great communication about the scope and potential impact. Though it was a low-severity issue, this was nevertheless something in need of patching and we're always grateful at PrivacySafe to security researchers, especially hardworking volunteers like Andrea.
    9 December, 2024
    Spinner:
Reported an XSS vulnerability on our website, and provided enough details for us to fix it quickly. So helpful!!