CyberKit

Drill Case

Decode Range

Name an opaque value before you read it: timestamps, encodings and hashes, all generated by the site's own converters.

The case

Every case leaves behind values that mean nothing until you know what they are: a bare integer in a log, a blob in a command line, a digest in a report.

Name what each value is first, then read it. The site's own converter and codecs generated every value here.

Foundational · about 55 minutes · 35 questions · 3 stages

  1. Timestamps 10 questions
  2. Encodings 12 questions
  3. Hashes 13 questions

What you will be able to do

  • Identify an epoch from a bare integer, using digit count as the first filter (Timestamp Converter)
  • Convert Unix seconds and milliseconds, Windows FILETIME, WebKit time and macOS absolute time to UTC
  • Say what a wrong-epoch reading would have produced, and why the arithmetic never flags it
  • Separate a storage format from a display rendering, and handle clock skew as a case fact rather than a conversion error
  • Recognize a timestamp format from the value alone, by its magnitude and length (Timestamp Converter)
  • Name the epoch behind FILETIME, WebKit and Mac Absolute Time, and say which direction each shifts a misread
  • Tell base64, hex and percent-encoding apart on sight and decode each (Deobfuscator)
  • Stop assuming a format and start identifying one: the step that prevents a silently wrong timeline
  • Identify a hash algorithm from the length of its digest (Hash Calculator & Verifier)
  • Read a prefixed format string ($2y$, $6$, …) and name the scheme it declares
  • Say when a digest is genuinely ambiguous, and why "32 hex characters" alone cannot separate MD5 from NTLM
  • Judge how much confidence an identification deserves, instead of reporting a guess as a fact

Read first: Timestamp Converter.

Notes for teaching it
  • The macOS question is the one to slow down on. Read as Unix it gives 1995: a real-looking date thirty-one years early, and nothing in the conversion complains.
  • The hex FILETIME question is where little-endian byte order comes up naturally. Worth writing the raw byte sequence on the board next to the value.
  • The last three questions are not arithmetic at all. If a group races through the conversions, those are where the time is better spent.
  • A good second drill after the network reference one, and the best warm-up before any timeline exercise.
  • The epoch questions are where the real lesson lands. A units mistake is out by a factor of ten and looks plausible; an epoch mistake is out by centuries and looks obviously wrong, which counter-intuitively makes the units mistake the more dangerous of the two.
  • Every timestamp shown is the SAME instant rendered in different formats, which is stated in the explanations. Worth pointing out: learners can check two answers against each other.
  • The values are generated by the site's own converter rather than typed in, so the drill and the Timestamp Converter cannot disagree. If a value here looks wrong, it is wrong in the tool too, and that is a bug worth reporting.
  • The hex-is-also-base64 point in the method is the one professionals still trip over. It is worth demonstrating live: paste a hex string into a base64 decoder and watch it cheerfully return garbage.
  • Short enough to use as a warm-up at the start of a session, or as the thing you hand to whoever finishes another exercise early.
  • The ambiguity questions are the point of the drill, not a trick. Learners trained on "hash length = algorithm" tables consistently answer these confidently and wrongly, which makes them the best discussion starter here.
  • Pair it with the Hash Calculator on screen: identifying a digest and then generating one from a known input in the same minute is what makes the length rule stick.

Terms behind it

Worksheet

Every question on one page, to print or to read without JavaScript. The answer key has the answers and why.

Timestamps, 10 questions
  1. A JSON log field reads "eventTime": 1772369229. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  2. The same log elsewhere carries 1771000000000. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  3. A parsed Registry key's last-write time is 134169616290000000. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  4. A hex dump of a FILETIME field reads 0x01DC5516EF7F2180. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  5. A browser history record carries the value 13415810602000000. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  6. A decoded property list holds a date value of 789639344. Convert it to UTC. Answer as YYYY-MM-DDTHH:MM:SSZ.

  7. You have a bare integer from an unfamiliar artifact and no documentation. What is the first thing to check?

    • The digit count, then whether each candidate epoch produces a date consistent with the rest of the case
    • Whether it converts cleanly as Unix seconds
    • Whether the file was created on Windows
    • The value's position in the record
  8. A Windows event log shows 09:14:22 in Event Viewer. A colleague in another country opens the same exported .evtx and sees 14:14:22. Who is right?

    • Both. The record stores UTC and each viewer renders it in the local zone of the machine displaying it
    • The first, because the log was written on that host
    • The second, because the export normalized the times
    • Neither, because exporting an event log rewrites its timestamps
  9. Which of these is stored in LOCAL time rather than UTC?

    • A FAT filesystem timestamp
    • A Windows event log record
    • An NTFS $STANDARD_INFORMATION timestamp
    • A Unix epoch value
  10. Two hosts' logs disagree by 47 seconds on the same event, and both are correctly converted to UTC. What do you do?

    • Record the offset, correct one source to the other, and state both in the timeline
    • Average the two timestamps
    • Trust the domain-joined host and discard the other reading
    • Treat them as two separate events
Encodings, 12 questions
  1. This timestamp appeared in an artifact: 1710408413 Which timestamp format is it?

  2. This value was pulled out of a script. Decode it and give the plaintext. d2hvYW1pIC9wcml2

  3. Windows FILETIME counts 100-nanosecond intervals from a different epoch than Unix time. Which year does the FILETIME epoch start in?

  4. This timestamp appeared in an artifact: 1710408413000 Which timestamp format is it?

  5. This value was pulled out of a script. Decode it and give the plaintext. 6e657420757365722061646d696e6973747261746f72

  6. Mac Absolute Time (Cocoa / CFAbsoluteTime) counts seconds from which year?

  7. This timestamp appeared in an artifact: 133548820130000000 Which timestamp format is it?

  8. This value was pulled out of a script. Decode it and give the plaintext. http%3A%2F%2F198.51.100.7%2Fa.ps1

  9. A Chrome history database stores visit times as a 17-digit number. Which epoch does the WebKit timestamp count from?

  10. This timestamp appeared in an artifact: 13354882013000000 Which timestamp format is it?

  11. This timestamp appeared in an artifact: 732101213 Which timestamp format is it?

  12. This timestamp appeared in an artifact: 638460052130000000 Which timestamp format is it?

Hashes, 13 questions
  1. Hashing the string "admin" with one of this tool's supported algorithms produced this digest: 21232f29 7a57a5a7 43894a0e 4a801fc3 That's 32 hex characters (128 bits). Which algorithm produced it? (e.g. "MD5", "SHA-256")

  2. Hashing the string "password123" with one of this tool's supported algorithms produced this digest: cbfdac60 08f9cab4 083784cb d1874f76 618d2a97 That's 40 hex characters (160 bits). Which algorithm produced it? (e.g. "MD5", "SHA-256")

  3. Hashing the string "root" with one of this tool's supported algorithms produced this digest: 4813494d 137e1631 bba301d5 acab6e7b b7aa74ce 1185d456 565ef51d 737677b2 That's 64 hex characters (256 bits). Which algorithm produced it? (e.g. "MD5", "SHA-256")

  4. Hashing the string "svc_backup" with one of this tool's supported algorithms produced this digest: 2eb894fa b92f51d6 aa26a2ce d87121f2 f6a1ec24 3763d924 3ab8776c f91c1440 e062a7a0 baa7bf8a d2c30e27 cc470c0e That's 96 hex characters (384 bits). Which algorithm produced it? (e.g. "MD5", "SHA-256")

  5. Hashing the string "administrator" with one of this tool's supported algorithms produced this digest: cf835de3 d4ea0136 7c45e412 e7a9393a 85a4e40a f149ed8c 3ed6c37c 05b67b27 813d7ff8 072c1035 cedd1941 5adf1712 8d63186f 05f0d656 002b0ca1 c34f44a0 That's 128 hex characters (512 bits). Which algorithm produced it? (e.g. "MD5", "SHA-256")

  6. An analyst finds this bare hex string pasted into a ticket, with no other context: 21232f29 7a57a5a7 43894a0e 4a801fc3 It's 32 hex characters. True or false: its format alone is enough to say with confidence that it's an MD5 digest and nothing else.

  7. The same Identify panel is given this 40-hex-character string: cbfdac60 08f9cab4 083784cb d1874f76 618d2a97 What confidence level (High/Medium/Low) does it assign to SHA-1 as the source?

  8. This string turns up in a leaked database dump: $2b$12$KIXQeYQ9Z5W8n1JlY0m0uOe3z7Q4rXk9pC2mN6sT1vB5dF7gH8jK9 What hashing scheme is this? (Short answer: name the format, e.g. "sha256", "crc32", "bcrypt".)

  9. This string turns up in a copied /etc/shadow line: $6$rounds=656000$abcXYZ123saltHere$Qk9z5W8n1JlY0m0uOe3z7Q4rXk9pC2mN6sT1vB5dF7gH8jK0m0uOe3z7Q4rXk9pC2mN6sT1vB5dF7gH8jK. What format is this? (short answer, e.g. "bcrypt", "md5crypt", "sha512crypt")

  10. Per the algorithm reference table, how many bits does a SHA-384 digest produce? (numeric answer)

  11. A batch of five digests just came off a triage script with no labels attached. Sort each one into the algorithm that produced it, using nothing but digest length.

  12. Same idea, different sort: these five strings are labeled only by how confidently the Hash Calculator's Identify panel can name their source. Sort each into its real confidence tier.

  13. The exact same 32-character hex string, 21232f297a57a5a743894a0e4a801fc3, turns up in four different places during an investigation. Sort each occurrence by what it most likely is, given where it was found.

Next: Map and Score. All drills