Up to 70% Off for Students & Emerging Markets - Apply Now

Contribute: All Guides
File / OSINT

Creating OSINT and File Challenges

Build a scenario, an optional file and flag questions directly in the challenge editor, then submit it for review.

OSINT and file-based challenges don't need a machine to run. Learners read a scenario, investigate public sources or a file you supply (an image, packet capture, document, dataset or sample), and submit answers. You build these directly in the challenge editor in your CyLynk dashboard, and they go live once a reviewer approves them.

How It Works

  1. Apply to contribute. Go to Contribute on the CyLynk website and select Apply to contribute. We review applications and you'll get an email when you're approved.
  2. Create the challenge in My Dashboard → Contribute → New challenge: the scenario, details and any file.
  3. Add the questions, each with its answer, points and an optional hint.
  4. Submit it for review. A reviewer publishes it, asks for changes or declines it. You're notified at each step.

The Contribute page on the CyLynk website

The application form

1. Plan the Challenge

Before you open the editor, have these ready:

  • A scenario with a clear goal: what the learner is investigating and why.
  • Questions in order, each with one exact answer the platform can check, such as a name, date, coordinates, hash or flag. Exploratory questions with no single answer can't be marked automatically, so rephrase them until they have one answer.
  • The file, if the challenge uses one.
  • A solution you've worked through yourself, so you know every answer can be reached from the brief and the file.

2. Responsible OSINT and Data Handling

  • Use public, lawfully obtained or properly authorised information only.
  • Prefer fictional or synthetic people, organisations and data. Don't expose real people's personal information.
  • Don't include passwords, tokens, private messages or personal documents you don't have permission to share.
  • Label simulated data and fictional scenarios as such.
  • If the challenge involves a real person, organisation or target, explain in the brief (or tell the reviewer in a note) why that's acceptable and what the training scope is.
  • Flag any website the challenge depends on that might change, disappear or need an account.

3. Create the Challenge

Go to My Dashboard → Contribute and select New challenge.

Your Contribute area

Fill in the editor:

Field What to enter
Title A clear name for the investigation
Card summary One sentence shown on the challenge card
Brief The scenario and what to find. This is everything the learner sees, so include any starting points, links and rules. Keep answers out of it
Category Choose the closest, such as Open-Source Intelligence, Steganography or Cryptography
Difficulty Easy, Medium, Hard or Insane
Estimated time Minutes a typical learner needs
Tags A few keywords, comma-separated (e.g. geolocation, exif)
Thumbnail Optional card image
Type and Who can take it Leave as they are. The reviewer sets these

The challenge editor

Select Create draft. You're taken to the challenge page to add the file and questions.

4. Add the File (Optional)

Adding the file

On the challenge page, upload one file of up to 100 MB: an image, packet capture, PDF, CSV, JSON, text file or archive. If you need several files, put them in one .zip.

Malware samples, exploits or executables must go inside a .zip protected with the password Hck4G00d. Otherwise browsers and antivirus will block or damage them. Tell learners the password in the brief. For example: "The sample is in sample.zip (password Hck4G00d)."

Create the zip with 7-Zip (7z a -tzip -pHck4G00d -mem=AES256 sample.zip sample/), Keka on macOS, or zip -er sample.zip sample/.

5. Add the Questions

Add a question for each thing the learner has to find, in the order they should answer:

  • Question: what to find, such as "In which city was the photo taken?"
  • Answer (flag): the exact accepted answer. Where the answer is a flag rather than a fact (a name, date or place), use the CyLynk format Lynk{...}. Answers are compared without case unless you tick Case-sensitive answer, and spaces at either end are ignored.
  • Flag format shown to learners (optional): shows the shape of the answer, such as Lynk{...} or YYYY-MM-DD. This avoids correct answers being rejected over formatting.
  • Points: how much the question is worth.
  • Hint (optional): a nudge for learners who are stuck.

Adding questions

Learners never see the answers.

6. Submit for Review

When the brief, file and questions are complete, select Submit for review. The challenge is locked while it's in review.

  • Changes requested: read the reviewer's feedback, edit the challenge and submit again.
  • Published: the challenge is live for learners.
  • Declined: the reviewer explains why. A declined challenge can't be resubmitted, but you can start a new one.

Limit: up to 10 challenges in draft or in review at a time.

Checklist

  • ☐ The brief explains the scenario and goal, and contains no answers
  • ☐ Every question has one exact answer, and you've solved them all from the brief and file
  • ☐ Flag formats are shown where the answer has a specific shape
  • ☐ Any malware, exploit or executable is in a .zip protected with Hck4G00d, and the brief gives the password
  • ☐ All data is public, authorised or fictional, with no real people's personal information
  • ☐ External sources that may change or need an account are mentioned
  • ☐ The challenge is submitted for review