Technology · Chapter 03

Reverse Engineering

Rebuild. Respect the law. Ship working software.

Reverse Engineering at UMT Techverse Chapter 03 challenges teams to reconstruct fully functional software inspired by existing products — only under legal restrictions. You may use modern AI and developer tools (Claude, GPT, GitHub Copilot, and related tooling) to accelerate analysis, design, and implementation. This module is a collaboration with the Business Innovation Module and is powered by Largify Solutions under the wing of UMT Techverse.

Winner: PKR 30,000 + Shield + Certificate
Entry: PKR 1,500 per team

Read the rules

Fee: PKR 1,500 per team
Team size: 1 to 3 members
Tools: Claude, GPT, GitHub tools, IDEs — allowed
Partner: Largify Solutions · BIM collaboration

BIM × Largify

Collaboration: Business Innovation Module · Powered by Largify Solutions under UMT Techverse. Fees and prize structure match the Cyber Hackathon module.

Prizes

What's on the line.

Winner
PKR 30,000 + Shield + Certificate
- Runner-up
  PKR 15,000 + Shield + Certificate
- All participants
  E-certificate

Guide

The rulebook.

Module intent

Rebuild selected product behaviours into a fully functional (or high-fidelity MVP) software system.
Demonstrate understanding of architecture, UX flows, data models, and implementation — not a slide-only pitch.
Collaborate across product thinking (Business Innovation) and engineering delivery (Largify Solutions guidance under UMT Techverse).

Legal restrictions (mandatory)

Do not infringe copyright, trademarks, patents, or trade secrets of any third party.
Do not redistribute proprietary binaries, cracked software, leaked source, paid datasets, or DRM-circumvention tools.
Do not scrape or attack live production systems without explicit written authorisation from the rights holder.
Public APIs, open-source licences, and your own original code are allowed — follow each licence’s terms.
Brand names of reference products may be mentioned for context, but your submission must use original branding unless you have permission.
If a task conflicts with law or university policy, stop and ask organisers — illegal work is disqualified.

Security expectations

Do not introduce malware, ransomware, credential stealers, or harmful payloads into demos or repos.
Do not target Techverse infrastructure, other teams, or campus networks beyond the sandbox you are given.
Store secrets in environment variables — never commit API keys or passwords.
If you discover a vulnerability in a third-party product during research, do not exploit it; report responsibly and do not include exploit PoCs that enable abuse.
Submissions may be checked for malicious content; unsafe packages can be rejected.

Allowed tooling

AI assistants: Claude, GPT, and comparable coding agents.
GitHub and standard developer tooling: repos, Actions (if safe), Copilot, issue trackers.
IDEs, browsers, debuggers, design tools, and open-source libraries under compatible licences.
Document which AI/tools you used in your final writeup — transparency is part of judging.

Deliverables

Working software demo (local or hosted) with clear setup instructions.
Short architecture note: what you rebuilt, what is original, and legal/compliance stance.
Repository or submission package with README, licence for your code, and demo credentials if needed.
Optional product one-pager linking to Business Innovation criteria (problem, users, value).

Judging focus

Functional completeness of the rebuilt experience.
Engineering quality: structure, reliability, and clarity.
Legal/ethical compliance and security hygiene.
Product thinking and presentation (collaboration with Business Innovation standards).
Responsible use of AI tools — augmentation, not unverified paste.

Rules of engagement

One team login / submission identity as assigned at registration.
No sabotage of other teams’ work or shared infrastructure.
Organiser decisions on eligibility, legality, and safety are final.
Breach of legal or security rules results in immediate disqualification and may be referred to university authorities.

FAQ

Frequently asked.

Can we copy proprietary source code from a commercial app?
No. You must rebuild functionality yourself (or with allowed tools) without stealing copyrighted code, assets, trademarks, or trade secrets.
Are AI tools allowed?
Yes — Claude, GPT, GitHub Copilot, and similar tools are allowed. You remain responsible for legality, originality of your submission, and security.
Is this linked to Business Innovation?
Yes. The module collaborates with the Business Innovation Module and is powered by Largify Solutions under UMT Techverse.
What must we demo?
A working product (or substantial MVP) that demonstrates reconstructed features, architecture clarity, and responsible engineering choices.

Contact & support

Rebuild responsibly.

For module queries contact the organising team. Registration support: registrations@umttechverse.com. Powered by Largify Solutions under UMT Techverse · collaboration with Business Innovation.

Ship something that runs, that you can defend legally and ethically, and that shows craft. Outstanding teams will be recognised for technical excellence, product clarity, and responsible engineering. Best of luck!

Module lead

TBA
Module Lead

More in Tech

All modules

Reverse EngineeringWinner PKR 30,000 + Shield + CertificateRegister