A web dashboard that gathers dark web data, unmasks hidden services, maps threat actors using PGP keys and wallets, and links rebranded personas to real-world entities.
National Technical Research Organisation (NTRO) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Data Gathering Engine
Continuously collects threat actor footprints and intelligence from dark web marketplaces, forums, and deep web sources.
Infrastructure De-anonymizer
Finds misconfigurations in Tor hidden services and matches them with clearnet infrastructure to point to origin servers.
Relationship Mapper
Maps threat actors across multiple marketplaces into a single graph connecting handles, PGP keys, wallets, and trust links.
AI Persona Profiler
Uses stylometric persona identification and behavioural profiling to link rebranded or migrated personas to known actors.
Analytical Front End
Provides a dashboard to query the intelligence database across timelines and export results in CSV, JSON, and report formats.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check if the system can autonomously gather data, correctly find misconfigurations in Tor services to link to origin servers, accurately map relationships across handles and wallets, and provide functioning export and query capabilities.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Which specific dark web sources or marketplaces must be targeted?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
What specific reliability thresholds make a source good quality?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
What accuracy percentage is expected for AI stylometric identification?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs data you may not get
The problem requires gathering data directly from dark web marketplaces and forums, which students cannot legally or safely access during a hackathon.
No measurable target
The description never states a required accuracy percentage for attribution confidence or persona linking.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for data gathering engine. How would you build that?
Decoded from SIH26151 itself — Continuously collects threat actor footprints and intelligence from dark web marketplaces, forums, and deep web sources. The brief asks for it by name.
The brief asks for infrastructure de-anonymizer. How would you build that?
Decoded from SIH26151 itself — Finds misconfigurations in Tor hidden services and matches them with clearnet infrastructure to point to origin servers. The brief asks for it by name.
The brief asks for relationship mapper. How would you build that?
Decoded from SIH26151 itself — Maps threat actors across multiple marketplaces into a single graph connecting handles, PGP keys, wallets, and trust links. The brief asks for it by name.
The brief asks for ai persona profiler. How would you build that?
Decoded from SIH26151 itself — Uses stylometric persona identification and behavioural profiling to link rebranded or migrated personas to known actors. The brief asks for it by name.
The brief asks for analytical front end. How would you build that?
Decoded from SIH26151 itself — Provides a dashboard to query the intelligence database across timelines and export results in CSV, JSON, and report formats. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will check if the system can autonomously gather data, correctly find misconfigurations in Tor services to link to origin servers, accurately map relationships across handles and wallets, and provide functioning export and query capabilities.
This is the evaluator read for your problem statement, decoded from the brief's own wording.