JengaSec Hack The Box
Partner
// JENGASEC_2026 :: RED_SIDE

JengaSec x Hack The Box. The hunt starts here.

Hack The Box has partnered with JengaSec 2026. Enter the Red side in a team of 4 through one online qualifier, Sunday 11 October 10:00 EAT to Monday 12 October 22:00 EAT.

This qualifier is how your team earns its seat to attend the JengaSec summit in person at Strathmore University, Nairobi.

RSVP by Saturday 10 October, 12:00 EAT.Every team member RSVPs individually.

RSVP on Meetup

Opens the qualifier event on the Hack The Box Kenya Meetup. Every member RSVPs individually.

RSVP_OPEN Teams of 4 SUN_11_OCT 10:00 EAT ONLINE
// The_Partnership

A global training ground.
A Kenyan proving ground.

Hack The Box has partnered with JengaSec 2026. The Red-side qualifier runs on Hack The Box Enterprise with the Hack The Box Kenya Meetup community.

Hack The Box is a cybersecurity upskilling platform with hands-on hacking labs used by individuals, universities and companies. Hack The Box Enterprise is its platform for teams.

// 01

The Gate

The qualifier runs on Hack The Box Enterprise. Qualifying is the route to Red-side registration.

// 02

The Community

The Hack The Box Kenya Meetup community has more than 4,000 members. Every team member RSVPs individually there.

// 03

The Test

Qualify online, then enter the Morani bug bounty hunt across the Blue-built application range at JengaSec.

Want your organisation on this page next year?Partner With JengaSec

// The_Gate

Registration is not a form.
It is something you earn.

No RSVP, no qualifier.No qualifier, no registration.

The entry route, not your team's current status.

  1. // Step_01

    RSVP on Meetup

    Your Meetup RSVP is your registration for the qualifier. It is the official record Hack The Box uses for the event, so every member of the team RSVPs individually.

    RSVP closes Saturday 10 October, 12:00 EAT. Every team is onboarded onto Hack The Box Enterprise and given a dedicated lab before the start. That takes time, so late RSVPs may not be accommodated.

    RSVP_OPEN
  2. // Step_02

    Get onboarded

    Every member needs an active Hack The Box Enterprise account. Access details are sent at onboarding.

    REQUIRED_BEFORE_START
  3. // Step_03

    Hunt the qualifier

    Sunday 11 October, 10:00 EAT to Monday 12 October, 22:00 EAT. One online CTF on Hack The Box Enterprise, played as a team of 4. The qualifying mark is published at onboarding.

    SUN_10:00 · MON_22:00_EAT
  4. // Step_04
    Only if your team qualifies

    Qualify, then register

    If your team passes, we contact you by email to confirm your team's place at the in-person sessions at Strathmore University. That email carries your registration access. Then register at jengasec.com/accounts/register/ before the event on 14 October.

    LOCKED_UNTIL_QUALIFIED
On qualifyingAn illustration of the rule. This page cannot read your team's status.
RSVP on Meetup

Teams that do not qualify cannot register for the Red side. Ilmurran, this is the only road in.

// The_Qualifier

One CTF. Sunday to Monday.
Online on Hack The Box.

Just finished a CTF this month? Good. You are warmed up.

  • Teams of 4
  • Every member aged 18 to 25
  • Free entry
// Opens
Sunday 11 October 2026, 10:00 EAT
// Closes
Monday 12 October 2026, 22:00 EAT
// Format
One CTF on Hack The Box Enterprise, 100% online.
// Hosted_By
Hack The Box Kenya Meetup x JengaSec.
// Team_Play
Teams of 4 play together. Every member is aged 18 to 25.
// Accounts
Every member needs an active Hack The Box Enterprise account.
// Onboarding
Everyone is onboarded before the start. Access details are sent at onboarding.
// Qualifying_Mark
Published at onboarding.
// Registration
Your Meetup RSVP is your registration for the qualifier. It is the official record Hack The Box uses for the event, so every member of the team RSVPs individually.
// RSVP_Deadline
Saturday 10 October, 12:00 EAT, at least 12 hours before the CTF opens. Every team is onboarded onto Hack The Box Enterprise and given a dedicated lab before the start. That takes time, so late RSVPs may not be accommodated.

Before Saturday noon. Every member ready.

  1. Every member RSVPs individually on the Hack The Box Kenya Meetup event.
  2. Every member has an active Hack The Box Enterprise account.
  3. Use the same name and email on Meetup, Hack The Box and JengaSec so the team can be matched.
  4. Agree a team of 4, with every member aged 18 to 25.
  5. Decide who writes the reports. A finding nobody can reproduce from the report scores nothing.
RSVP on Meetup

What you are playing for: a seat to attend the JengaSec summit in person at Strathmore University, Nairobi. The qualifier is the only way onto the Red side.

If your team passes, we reach out to you. Once results are confirmed, JengaSec emails every qualifying team to confirm the team is coming to the in-person sessions at Strathmore University, and sends its registration access. You do not need to chase us. Teams then register at jengasec.com/accounts/register/ before the event on 14 October. That registration gives the team access to all three days of JengaSec 2026, 14 to 16 October at Strathmore University, Nairobi.

Teams that do not qualify cannot register for the Red side.

Green opens the gate.Red is the hunt.

// THE_HUNT :: MORANI_HUNTING_GROUNDS

One range. Every team hunting.
First valid report wins a duplicate.

Morani Hunting Grounds is the Application Red track. At JengaSec 2026, 14 to 16 October at Strathmore University, Nairobi, it runs as a bug bounty hunt across the Blue-built application range. There is no proposal round for Red.

// 01

The range is the programme

The nine Blue-built application cells are the programme. The scope list is published when the hunting window opens. Anything not on it is out of scope.

// 02

Severity scores

Findings score by severity. The scoring table is in the welcome pack.

// 03

First valid report

The first valid report wins a duplicate.

// 04

Reproducible reports

A finding nobody can reproduce from the report scores nothing.

// 05

Every request is yours

Every request must be attributable to the team.

// Rules_Of_Engagement
  • Stay in scope.
  • No denial of service.
  • No attacks on event infrastructure, other teams, judges or organisers.
  • Stop and report if you reach real personal data.

Full rules of engagement are issued in the welcome pack.

// The_Targets

Nine kinds of target.
Read what they had to get right.

These are the targets in the programme. Every Blue team building one was given the same requirements you are reading now. Your job is to find where they fell short.

Internet Banking Portal

The customer web front door: balances, transaction history, statements, transfers and profile.

// What_You_Will_Try
  • Authentication bypass, session fixation and hijacking, horizontal privilege escalation between customers, business-logic abuse of the beneficiary and transfer flow, and forced browsing to unlinked endpoints.
// What_Blue_Had_To_Get_Right
  • Server-side authorisation on every request.
  • Session lifetime, invalidation and secure cookie attributes.
  • A cooling-off period or step-up authentication before a newly added beneficiary can receive funds.
  • Defence against injection, cross-site scripting, cross-site request forgery, insecure direct object reference and open redirect.
  • Rate limiting and lockout on all authentication and money-movement paths.
  • Statements generated server-side with authorisation checked at generation, not merely at link time.
  • A full audit trail the customer can retrieve.

Mobile Banking API

The same bank for a client that cannot be trusted to enforce anything, on a device that may be compromised.

// What_You_Will_Try
  • Token theft and replay across devices, refresh-token abuse, idempotency and race-condition attacks on transfers, mass assignment, and API enumeration for unprotected endpoints.
// What_Blue_Had_To_Get_Right
  • Device registration and binding so a token issued to one device cannot be replayed from another.
  • Short-lived access tokens with refresh-token rotation and reuse detection.
  • Transaction signing or step-up confirmation independent of the session token.
  • Idempotency keys on every state-changing endpoint.
  • Strict schema validation that rejects unknown fields rather than ignoring them.
  • Per-device and per-account rate limiting.
  • No sensitive data in URLs, logs or error messages.

Customer Authentication and Identity Service

The identity provider every other cell trusts. The most security-dense brief in the catalogue.

// What_You_Will_Try
  • Credential stuffing, user enumeration through timing or message differences, MFA bypass through flow manipulation, token forgery and algorithm confusion, password-reset token prediction or reuse, and race conditions in enrolment.
// What_Blue_Had_To_Get_Right
  • Credential storage using a modern memory-hard password hash with per-user salt and a breached-password check.
  • Multi-factor authentication with at least two second factors, plus recovery codes issued once and stored hashed.
  • Signed short-lived tokens with audience and issuer claims, key rotation, and a published JWKS endpoint.
  • Token revocation and introspection so a compromised session ends enterprise-wide within seconds.
  • Password reset that does not disclose account existence, uses single-use time-limited tokens and invalidates all sessions.
  • Progressive lockout resistant to both targeted brute force and credential-stuffing sprays.
  • Risk signals on every authentication: new device, new location, impossible travel, unusual hour: emitted even when the login is allowed.
  • A tamper-evident audit log of every identity event.

Payment Processing Service

The service that actually moves money: the ledger, the rules that govern a transfer, and the controls that stop money moving when it should not.

// What_You_Will_Try
  • Race conditions and time-of-check-to-time-of-use attacks on balance, negative and precision-abuse amounts, currency and rounding manipulation, replay of payment instructions, limit bypass through decomposition, and forging or replaying the settlement webhook.
// What_Blue_Had_To_Get_Right
  • A double-entry ledger where balance is derived from entries and never from a mutable field.
  • Atomic, isolated transfer execution provably safe under concurrent requests.
  • Idempotency on every payment instruction with a defined retention window.
  • Per-transaction, daily and velocity limits evaluated server-side.
  • A rules-based fraud check producing allow, review or block with a recorded reason, and a reviewable queue.
  • Maker-checker approval above a defined threshold where the approver may not be the initiator.
  • Reversals and refunds as compensating entries, never as mutation of history.
  • An append-only transaction log with independently verifiable sequence integrity.
  • End-of-day reconciliation that proves the ledger balances.

Loan Origination System

Application to decision: a multi-stage workflow with document upload, automated scoring, human approval and a disbursement instruction.

// What_You_Will_Try
  • Workflow-stage skipping, insecure direct object reference across applicants, malicious file upload and path traversal, tampering with declared income or score inputs, and privilege escalation from applicant to assessor or approver.
// What_Blue_Had_To_Get_Right
  • Stage transitions enforced server-side and impossible to skip by manipulating client state.
  • Document upload with content-type verified by inspection rather than by extension, size limits, malware scanning, and storage in the private bucket.
  • Documents served only through authorised, short-lived, single-use links with non-guessable references.
  • A deterministic credit-scoring component with a recorded input snapshot so any decision can be reproduced.
  • Segregation of duties between applicant, assessor and approver.
  • An approval authority matrix by amount, enforced in code, with an escalation path.
  • Disbursement issued only after approval, signed, idempotent, and impossible to trigger from the applicant's session.
  • Defined retention and deletion for the personal and financial documents collected.

Internal Back-Office Portal

The staff-facing system where tellers, supervisors and administrators service customer accounts. The highest-privilege application in the enterprise.

// What_You_Will_Try
  • Privilege escalation between staff roles, forced browsing to administrative functions, maker-checker bypass through self-approval or replay, mass data extraction through search and export, and abuse of elevation flows.
// What_Blue_Had_To_Get_Right
  • Role-based access control with at least four staff roles whose permissions genuinely differ, enforced server-side for every action and never merely hidden in the interface.
  • Maker-checker on every high-impact action, with a different and more senior checker.
  • Mandatory structured reason codes on every privileged action.
  • Just-in-time elevation, time-boxed and automatically revoked.
  • Data minimisation by role, with masked account and identity numbers and unmasking as a separately audited action.
  • Administrative access restricted by network origin.
  • Session controls suited to a shared workstation: short idle timeout, explicit lock, concurrent-session limits.
  • A tamper-evident audit log viewable by an auditor role that cannot modify customer data.
  • Detection and alerting on insider-abuse patterns: bulk record access, out-of-hours activity, repeated access to one customer, and self-servicing of an employee's own accounts.

Customer Support and Ticketing System

Free text and file attachments moving between two parties at very different privilege levels, with identity verification under pressure.

// What_You_Will_Try
  • Stored cross-site scripting aimed at agents, insecure direct object reference across tickets, leakage of internal notes into the customer view, malicious attachments, and social-engineering flows that trick the system into treating an unverified caller as verified.
// What_Blue_Had_To_Get_Right
  • Ticket lifecycle with an immutable conversation thread.
  • Two-sided messaging where internal notes are provably invisible to the customer.
  • Attachment upload from both sides with type verification by inspection, size limits, malware scanning, and rendering that cannot execute in the browser.
  • Structured customer identity verification before any account-affecting action, with method and outcome recorded on the ticket.
  • Output encoding everywhere customer-supplied text is rendered, including the agent interface: the higher-value cross-site scripting target.
  • Rate limiting on ticket and message creation.
  • A defined, enforced boundary: anything touching money or credentials is handed to the back-office portal rather than performed here.
  • Detection and masking at ingestion of credentials or card numbers pasted into a ticket.

Fraud and Transaction Monitoring Service OPTIONAL BRIEF

Near-real-time scoring of transactions from the payments service, with case management for analysts and a feedback loop.

// What_You_Will_Try
  • Score evasion through transaction shaping, case tampering, suppression of alerts, and poisoning of the feedback loop.
// What_Blue_Had_To_Get_Right
  • Scoring that consumes the payments ledger rather than duplicating it.
  • Analyst role-based access control and case-level authorisation.
  • Tamper-evident case history where decisions cannot be rewritten.
  • Customer notification that does not itself disclose account detail.
  • An analyst feedback loop that the customer cannot poison, and integrity protection on the rule set itself.

Notifications and Statements Service OPTIONAL BRIEF

Outbound email, SMS and push, plus server-generated account statements.

// What_You_Will_Try
  • Account enumeration through notification behaviour, statement link prediction, template injection, and notification flooding used as cover for other activity.
// What_Blue_Had_To_Get_Right
  • Authorisation checked at generation time, not at link time.
  • Short-lived signed document links that are not guessable or enumerable.
  • Template rendering safe against injection.
  • Data minimisation in every message body.
  • Rate limiting, and a full delivery audit trail.

Full application briefs, with every security requirement a judge will check, are issued in the welcome pack when registration completes.

// Once_You_Qualify

Have this ready.
For when you qualify.

If your team passes the qualifier, we email you to confirm your place at the in-person sessions at Strathmore University, with your registration access. Prepare these items now. Register only after your team qualifies.

  • Full legal name of every member, exactly as on their identity document.
  • Identity document per member showing date of birth. PDF, JPG or PNG, under 5 MB, photographed in good light with the whole document in frame.
  • Email per member, institutional if you have one.
  • GitHub or GitLab handle per member.
  • If enrolled: student number, institution, programme and year of study.
  • Captain and one deputy: phone number in international format, for example +254712345678.
  • Team name, three to forty characters.
  • Ranked track preferences for your side.
  • Skills declaration, 100 to 1500 characters, honestly describing what the team has built before. Overstating it earns you a brief you cannot complete.
JengaSec Hack The Box
// Final_Word

Saturday 10 October, 12:00 EAT.
Every member RSVPs.

Baraka, Ilmurran.

Questions? sucybersec@strathmore.edu