Bug bounty program
MG
MTN Group
Most upvoted reports128
All reports| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| SQL Injection on cookie parameterAnalysed#761304 | SQL Injection | 2020-05-03 | – | 323 |
| SQLi | in URL pathsAnalysed#2958619 | SQL Injection | 2025-03-06 | – | 149 |
| IDOR at mtnmobad.mtnbusiness.com.ng leads to PII leakage.Analysed#1773609 | Insecure Direct Object Reference | 2024-10-05 | – | 135 |
| Yet Another OTP code Leaked in the API ResponseAnalysed#2635315 | Authentication | 2025-01-08 | – | 135 |
| FULL ACCOUNT TAKEOVERAnalysed#2542372 | No weakness recorded | 2024-08-17 | – | 123 |
| SQL injection in URL path leads to Database AccessAnalysed#2633959 | SQL Injection | 2025-01-08 | – | 115 |
| Authentication Bypass Leads To Complete Account TakeveOver on ██████████Analysed#1709881 | Authentication | 2024-09-14 | – | 109 |
| DOM Based Reflected Cross Site ScriptingAnalysed#2321874 | Cross-site Scripting | 2024-12-25 | – | 104 |
| Reflected cross site scripting (XSS) attacks Reflected XSS attacks,Analysed#1799197 | Cross-site Scripting | 2024-08-30 | – | 100 |
| Ability to Add and Verify Uncontrolled Mobile Numbers Leading to Account Takeover (ATO)Analysed#2762462 | Authentication | 2025-03-04 | – | 98 |
Subdomains214,285
| Name | Scope | First seen |
|---|---|---|
| 5gmaps.mtn.zm | Not in the scope | 2026-11-14 |
| auth.mtn.zmauth | Not in the scope | 2026-11-14 |
| callertunes.mtn.zm | Not in the scope | 2026-11-14 |
| chezapay.mtn.zm | Not in the scope | 2026-11-14 |
| api.chezapay.mtn.zmapi | Not in the scope | 2026-11-14 |
| dev.chezapay.mtn.zmdev | Not in the scope | 2026-11-14 |
| staging.chezapay.mtn.zmstaging | Not in the scope | 2026-11-14 |
| cpassmessaging.mtn.zm | Not in the scope | 2026-11-14 |
| ena.mtn.zm | Not in the scope | 2026-11-14 |
| grafana-vm-vas-sm.mtn.zmmonitoring | Not in the scope | 2026-11-14 |
| home.mtn.zm | Not in the scope | 2026-11-14 |
| isl.mtn.zm | Not in the scope | 2026-11-14 |
| isluat.mtn.zm | Not in the scope | 2026-11-14 |
| mobileadvertising.mtn.zm | Not in the scope | 2026-11-14 |
| mtnfleetplatform.mtn.zm | Not in the scope | 2026-11-14 |
| www.mtnfleetplatform.mtn.zm | Not in the scope | 2026-11-14 |
| mtnid.mtn.zm | Not in the scope | 2026-11-14 |
| mtnmomo.mtn.zm | In scope | 2026-11-14 |
| www.mtnmomo.mtn.zm | Not in the scope | 2026-11-14 |
| my5g.mtn.zm | Not in the scope | 2026-11-14 |
| myreg.mtn.zm | Not in the scope | 2026-11-14 |
| www.myreg.mtn.zm | Not in the scope | 2026-11-14 |
| oam-vm-vas-sm.mtn.zm | Not in the scope | 2026-11-14 |
| partnergui.mtn.zm | In scope | 2026-11-14 |
| www.partnergui.mtn.zm | Not in the scope | 2026-11-14 |
| rbtcallback.mtn.zm | Not in the scope | 2026-11-14 |
| rbtcms.mtn.zm | Not in the scope | 2026-11-14 |
| rebalancer.mtn.zm | Not in the scope | 2026-11-14 |
| rechargeandwin.mtn.zm | Not in the scope | 2026-11-14 |
| selfservice.mtn.zm | Not in the scope | 2026-11-14 |
| smartphones.mtn.zm | Not in the scope | 2026-11-14 |
| speedtest.mtn.zm | Not in the scope | 2026-11-14 |
| talktoussurvey.mtn.zm | Not in the scope | 2026-11-14 |
| travelesim.mtn.zm | Not in the scope | 2026-11-14 |
| www.travelesim.mtn.zm | Not in the scope | 2026-11-14 |
| valuebooster.mtn.zm | Not in the scope | 2026-11-14 |
| vm-vas-sm.mtn.zm | Not in the scope | 2026-11-14 |
| api.vm-vas-sm.mtn.zmapi | Not in the scope | 2026-11-14 |
| webreg.mtn.zm | Not in the scope | 2026-11-14 |
| backend.webreg.mtn.zm | Not in the scope | 2026-11-14 |
| www.backend.webreg.mtn.zm | Not in the scope | 2026-11-14 |
| mail.webreg.mtn.zmmail | Not in the scope | 2026-11-14 |
| www.webreg.mtn.zm | Not in the scope | 2026-11-14 |
| www.mtn.zm | In scope | 2026-11-14 |
28 names are covered by the program's own scope; 2 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.