osintfreeeasy

HAZMAT II

metactf

Task: identify the storage container type from a truck photo showing radioactive UF6 transport markings. Solution: interpret the visible regulatory labels and choose the broader package classification, TYPE B(U), rather than the model name or inner cylinder type.

$ ls tags/ techniques/
label_based_osinttransport_classification_lookupregulatory_marking_interpretation

HAZMAT II — metactf

Description

I saw another crazy looking truck! This one looks even scarier... can you identify the type of storage container being used here?

English summary: the image shows a radioactive uranium hexafluoride transport package with several regulatory markings. The goal is to determine which container type the challenge expects from the visible labels.

Analysis

The key evidence in the image is the combination of transport and certificate markings:

  • RADIOACTIVE MATERIAL / URANIUM HEXAFLUORIDE / FISSILE / UN 2977
  • USA/9196/B(U)F-96
  • TYPE B(U)
  • UX-30
  • gross weight about 8270 lbs / 3751 kg

Research shows that UX-30 is the specific model designation for the overpack/package used to transport UF6 cylinders. That makes it a real and relevant identifier, but it is more specific than the challenge's accepted answer.

The important distinction is between:

  • 30B cylinder: the inner uranium hexafluoride cylinder, not the exterior transport package visible on the truck
  • UX-30 / UX-30 overpack: the exact model name of the package
  • TYPE B(U): the regulatory package class printed directly on the container itself

TYPE_B_PACKAGE is correct because the challenge asked for the type of storage container, and the visible accepted classification on the outer package is TYPE B(U). The flag normalizes that broader package class to TYPE_B_PACKAGE. Alternatives like UX_30 or UX_30_OVERPACK are too model-specific, while 30B_CYLINDER refers to the inner cylinder rather than the container seen in the image.

Solution

...

🔒

Permission denied (requires auth)

Sign in to read this free writeup

This writeup is free — just sign in with GitHub to read it.

$ssh [email protected]