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

Contribute: All Guides
Virtual machine

Submitting a Virtual Machine Lab

Export your vulnerable VM, pack it with its flags and instructions into one password-protected archive, and upload it from your dashboard.

A VM lab is a vulnerable machine that learners attack over the network from the browser-based AttackBox or the VPN. You export the VM, pack it with its documentation into one password-protected .zip or .7z, and upload it from your CyLynk dashboard. Our team imports it into AWS, sets it up on the platform and writes the final learner instructions from what you provide.

You don't need AWS access, a file-transfer service or any infrastructure of your own.

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. Build and export the VM so it meets the requirements below.
  3. Pack it into one .zip or .7z protected with the password Hck4G00d.
  4. Create the lab in your dashboard (My Dashboard → Contribute → New VM lab), paste your README and upload the archive.
  5. Submit it for review. A reviewer approves it, asks for changes or declines it. You're notified at each step.
  6. We import it and publish it. You're notified when it goes live.

The Contribute page on the CyLynk website

The application form

1. Platform Requirements

We import VMs with AWS VM Import/Export, so the VM must meet its requirements: https://docs.aws.amazon.com/vm-import/latest/userguide/prerequisites.html

Requirement What we need
Architecture x86_64 only. ARM64 VMs and physical-to-virtual (P2V) conversions are not supported.
Disk format OVA (preferred), stream-optimised VMDK, VHD, VHDX or RAW (.raw / .img). QCOW2 and VDI are not supported, so ask us before converting from them.
Boot mode BIOS or UEFI. Record which in the README.
Networking The primary network interface uses DHCP. Don't rely on a fixed IP address.
Learner access Learners reach the VM over the network only, never through its desktop or console. Document every service, port and protocol they need.
Windows Enable Remote Desktop (RDP) on TCP 3389 and allow it in the Windows firewall. We use it to tell when the VM is ready. Turn off automatic updates.
Fresh every session Each learner gets a fresh copy of the VM, and nothing is kept between sessions.
Size Keep disks no bigger than the lab needs. The upload limit is 100 GB per archive.
Licensing State the OS licence. Windows evaluation or retail licences usually can't be moved to AWS, so we may replace them with AWS-provided licensing during import.

2. Security and Content Rules

The VM may contain deliberate teaching vulnerabilities. It must not:

  • phone home, exfiltrate data, mine cryptocurrency or contact any outside server
  • contain real malware outside the agreed lab scope, real credentials, API keys or anyone's personal data
  • include software or data you don't have permission to share
  • be built to attack anything outside the lab

Use throwaway credentials made for the lab only. Monitoring agents, licence checks or hypervisor-specific tools can stop the VM running on AWS, so list any that are installed in the README.

3. Prepare and Export the VM

  1. Test the lab from a clean boot and solve every flag yourself.
  2. Shut the VM down cleanly. Don't export a suspended or saved-state VM.
  3. Export it with your hypervisor's export tool:
  4. Check the export finished without errors and that every disk file is there.
  5. Keep your original VM until the lab is live.

4. What Goes in the Archive

my-lab.7z   (password: Hck4G00d)
└── my-lab/
    ├── LEARNER.md      the scenario and instructions learners follow
    ├── flags.md        every question, its answer, points and an optional hint
    ├── solution.md     a walkthrough showing how each flag is reached
    └── lab/
        └── my-lab.ova  the exported VM (or its VMDK / VHD / VHDX / RAW disks)
  • flags.md lists the questions in the order learners answer them. For each one, give the exact answer, the points and an optional hint. Flags use the CyLynk format Lynk{...}, for example Lynk{j3nk1ns_scr1pt_c0ns0le}. Learners never see this file.
  • LEARNER.md is what learners read: the scenario, what to find, how to reach the machine and any throwaway login details they need.
  • Keep exported file names as they are, and don't leave out any disk files.

5. Create the Password-Protected Archive

Every lab archive uses the same password: Hck4G00d. For VMs we recommend .7z, which handles very large files well and usually compresses disk images a lot, so the upload is faster.

Why a password? Labs contain deliberately vulnerable software, and antivirus or email filters often delete or quarantine it in transit. The password keeps those tools out. It isn't a secret, so it doesn't protect anything sensitive. Never put real credentials in a lab.

Windows (7-Zip): right-click the my-lab folder → 7-Zip → Add to archive…. Set Archive format to 7z (or zip), enter Hck4G00d as the password and select OK.

macOS (Keka): choose 7Z (or ZIP), enable Encrypt and enter Hck4G00d, then drag the folder onto Keka.

Linux or macOS (7-Zip command line):

7z a -t7z -pHck4G00d -mhe=on my-lab.7z my-lab/
7z t -pHck4G00d my-lab.7z       # check it opens with the password

If you use .zip, make sure your tool supports files over 4 GB (ZIP64). 7-Zip and Keka do.

6. Write Your README

The README is pasted into the form, not uploaded, so reviewers can read it without downloading a large file. Include:

Section What to write
About Lab name, a short description, difficulty (Easy, Medium, Hard or Insane), estimated time, and what learners will learn
Operating system OS, edition and exact version
Disk Export format, number of disks, total disk size, and the vCPUs and memory it needs
Boot mode BIOS or UEFI
Services and ports Every service learners reach, with its port and protocol (for example HTTP 80, SMB 445, RDP 3389)
Credentials Throwaway logins learners or we need, and which are for learners and which are just for us
Internet access Whether the lab needs it and why
Licence OS licence type and any software licences
Test steps What should be running after boot, and how we can check it
Known issues First-boot steps, slow services, limitations. Write "None" if there are none

7. Upload and Submit in Your Dashboard

  1. Go to My Dashboard → Contribute and select New VM lab.

    Your Contribute area

  2. Enter a title and a two- or three-sentence summary, paste your README, then choose your archive and select Create and upload.

    Creating a VM lab

  3. Keep the tab open while it uploads. Large VMs can take a while. If the upload is interrupted (closed laptop, lost connection), open the lab again and choose the same file to resume where it stopped.

  4. When the upload finishes, select Submit for review. The lab is locked while it's in review.

    A lab ready to submit

Limits: up to 100 GB per file, 5 labs in progress at a time and 200 GB of uploads in total.

8. After You Submit

  • Changes requested: read the reviewer's feedback, fix the VM, upload a new archive if needed and submit again.
  • Approved: our team imports the VM into AWS and sets up the lab. You don't need to do anything else.
  • Live: you're notified when learners can use it.
  • Declined: the reviewer explains why. A declined lab can't be resubmitted, but you can start a new one.

Checklist

  • ☐ The VM is x86_64, in a supported format, and its boot mode is recorded
  • ☐ It uses DHCP and learners reach it over the network only
  • ☐ Windows: RDP is on TCP 3389, allowed in the firewall, and automatic updates are off
  • ☐ Every flag can be solved from a fresh boot
  • ☐ The VM was shut down cleanly and exported without errors
  • ☐ No real secrets, personal data or content you can't share
  • ☐ The archive contains LEARNER.md, flags.md, solution.md and the VM in lab/
  • ☐ The archive is a .7z or .zip protected with Hck4G00d and opens correctly
  • ☐ The README is pasted into the form, the upload has finished, and the lab is submitted for review