Disclosure
[redacted] Security Assessment Report 2026
The following critical credentials are hardcoded in the JS bundle: Security Config File (Publicly Accessible) These values are used as custom headers in login requests: | JWT Secret | `YOUR_VERY_CONFIDENTIAL_SECRET_FOR_SIGNING_JWT_TOKENS!!!` | Mock auth (Fuse framework) |
- Target
- African Fintech
- Category
- JWT Issues
- Channel
- Responsible Disclosure
- Disclosed
- 2026-03
Redaction note
Vendor identity withheld.
This finding is documented here as part of MemCyber’s public disclosure record. The vendor has been anonymized to a sector and region descriptor. Full technical detail — including root cause, reproducible proof-of-concept, remediation guidance, and vendor attribution where granted — is available to qualified prospects under NDA.
Coordinated disclosure
How we handled it.
- Reported to the vendor via Responsible Disclosure with a reproducible proof-of-concept.
- Triage + remediation window coordinated with the vendor security team.
- Fix verified before any public reference.
- This record published only after the embargo period closed.