Security
Bug Bounty Program
Found a security issue in Siberaman? Report it to us privately. Valid reports earn up to Rp5.000.000.
How it works
- 01
Find and verify. Confirm the issue is in scope, reproducible, and has real security impact.
- 02
Write the report. Use the template below. Include clear steps, a working proof of concept, and the impact you observed.
- 03
Send it securely. Email [email protected] with the subject
[BUG BOUNTY]followed by a short title. - 04
Triage and fix. We confirm, rate severity with CVSS 4.0, and keep you updated until the fix ships.
- 05
Get rewarded. Rewards are paid by bank transfer or e-wallet within 14 days of validation.
Show the report template
Subject: [BUG BOUNTY] <short title of the issue>
Researcher handle : <your name or handle>
Asset : <e.g. siberaman.id/api/search>
Vulnerability : <e.g. SQL injection>
Suggested CVSS 4.0: <vector string and score>
Summary
<one or two sentences describing the issue>
Steps to reproduce
1.
2.
3.
Proof of concept (required)
<request/response, payload, screenshots, or a short video>
Impact
<what an attacker could realistically achieve>
Suggested remediation (optional)
<how you would fix it>Rewards
Critical
Rp3.000.000 – Rp5.000.000
Remote code execution, full server takeover, mass exposure of stored data.
High
Rp1.500.000 – Rp3.000.000
Authentication bypass, SSRF reaching internal services, Cloak vault decryption without the password.
Medium
Rp500.000 – Rp1.500.000
Path traversal that reads non-public files, file upload flaws without code execution, UniAI prompt injection that leaks limited data.
Low
No cash reward
Limited information disclosure, security misconfiguration with a demonstrable impact.
Informational
No cash reward
Best-practice gaps without a practical exploit path.
- Amounts are for Tier 1 assets. Tier 2 assets get up to 70% of them.
- Severity follows CVSS 4.0, adjusted for the real impact.
- No working proof of concept, no reward. Details added after triage do not change the reward.
- Clear reports with a clean proof of concept can earn a bonus.
What you can test
siberaman.idTier 1
Public site, search, articles, resources, and public APIs under /api.
Cloak for Windows and macOSTier 1
Latest release from siberaman.id/cloak. Vault encryption, recovery, and app isolation.
uniai.siberaman.idTier 2
Includes prompt injection that leads to data exposure or unauthorized actions.
feed.siberaman.idTier 2
SiberFeed reader and its public endpoints.
translator.siberaman.idTier 2
Translator service and its upload handling.
Do not test
- Any *.siberaman.id host not listed above, including staging, mail, and analytics hosts
- Third-party services we use (Google Analytics, Sentry, hosting and CDN providers); report those to the vendor
- Physical attacks against Siberaman offices, staff, or infrastructure
- Social engineering, phishing, or vishing of Siberaman staff or users
- Older Cloak builds that are no longer offered for download
What we reward
We reward
- Remote code execution and command or template injection
- SQL, NoSQL, and other injection flaws
- Authentication and session-management bypass
- Privilege escalation, such as a normal account gaining admin rights
- Server-side request forgery (SSRF)
- Path traversal and unrestricted file upload
- Cryptographic flaws in Cloak vault storage or recovery
- Prompt injection in UniAI that leaks data or performs actions
We don't reward
- IDOR, cross-site scripting (XSS) of any type, and CSRF
- Reports from automated scanners without a validated, exploitable impact
- Missing security headers or cookie flags without a working exploit
- Clickjacking on pages without sensitive actions
- Rate limiting or brute force on non-authentication endpoints
- SPF, DKIM, or DMARC configuration findings
- Banner grabbing and software version disclosure
- Issues that need a compromised device
- Denial of service, including volumetric and resource exhaustion
- Publicly known CVEs disclosed less than 30 days ago
- Content spoofing or text injection without HTML or link rendering
- Reports without a working proof of concept, including theoretical issues
Rules
Use your own accounts
Only test against accounts and data you own or that we issued to you. Stop and report as soon as you reach anyone else's data.
Keep it minimal
Access, change, or keep only the data needed to prove the issue. Never download, keep, or share data that does not belong to you.
No disruption
No denial of service, spam, or degrading the experience for other users. Keep automated testing under 10 requests per second.
Identify your traffic
Add the header
X-Bug-Bounty: <your-handle>to your requests so we can tell your traffic apart from a real attack.Keep it confidential
Do not disclose the issue publicly or to third parties until it is fixed and we have agreed to disclosure in writing.
One issue per report
Send each vulnerability separately unless chaining is needed to show impact. The first valid report of an issue receives the reward.
Answer for your tools
You are responsible for every request and action made by the scanners, scripts, or AI agents you run. If they go beyond scope or affect other users, the report loses its reward.
Verify what you send
You may use AI to help write a report, but check every claim and proof of concept yourself. Unverified AI-generated reports are closed without a reward.
Breaking these rules can cost you the reward and the safe harbor protection.
Response times
- First response
- Within 2 business days
- Triage and severity
- Within 5 business days
- Reward payment
- Within 14 days of validation
- Critical fix
- Within 7 days
- High fix
- Within 30 days
- Medium and Low fix
- Within 90 days
Fix times start when we validate the report.
Safe harbor
If you follow this policy in good faith, we consider your research authorized. We will not take legal action against you or report you to the police, including under the UU ITE law. If someone else takes legal action against you for research covered by this policy, we will make it clear that you followed it.
This does not cover harming users, taking more data than needed to prove an issue, disrupting services, or breaking the rules above. Not sure? Ask us first at [email protected].
FAQ
01Who can join the program?
Anyone can take part, except current Siberaman staff, contractors, and their immediate families. You must follow these rules and any laws that apply to you.
02How are rewards paid?
Rewards are paid in Indonesian rupiah by bank transfer or e-wallet after we validate the report. We may ask for identity details needed for payment and tax purposes.
03What if two people report the same issue?
The first complete, valid report we receive gets the reward. Later duplicates are acknowledged but not rewarded, unless they add significant new impact.
04Can I publish a write-up?
Yes, after the issue is fixed and we approve it in writing. We usually agree within 30 days of the fix and can review your draft to make sure no sensitive data is included.
05How do you decide severity?
We use CVSS 4.0 as a baseline and adjust it for the real business impact on Siberaman. If you disagree with a rating, reply to the report and we will review it again.
06Can I use AI tools?
Yes, to help find issues or write reports. You are responsible for everything your tools do and everything you send. Unverified AI-generated reports are closed without a reward, and repeated ones can get you removed from the program.
07Can I test the Cloak desktop app offline?
Yes. Cloak is local-first, so you can test it on your own device freely. Do not distribute modified builds or target other people's machines.
