Two unclear photographs and one strange UFO hint lead to an Infosys campus in Bengaluru. The useful skill is connecting architecture, context, and provenance—not trusting the first similar roof.
1. Observe the photographsRoof gap, glazing, central supportThe write-up reports no useful image metadata.
2. Pivot on the wordingUFO hint → pyramid hypothesisA thematic association supplies a new search direction.
3. Corroborate the campusInfosys → Bengaluru → landmarksCompare both views and their surroundings, not just a silhouette.
4. Assemble the answerNames + building number + yearKeep reported acceptance separate from independent photo verification.
The dashed stage is the evidence checkpoint: a promising search result becomes a location claim only after corroboration. UFO theories are a puzzle lead, not factual evidence.
The challenge in plain English
The original challenge reportedly shipped a ZIP containing two images. Its description reads:
“The UFO that came to earth mistook this for something else.”
Supplied write-up, page 1
You need the location, city, building names for the two pictures, and the photo year. The author first tried metadata and reverse image search, then used the UFO wording to look for a pyramid-shaped building. That lead pointed to Infosys; Google Maps comparisons reportedly narrowed the setting to Bengaluru.
The write-up finishes with 2008 already in the candidate and reports finding 50 by trying building-number candidates. It records an accepted flag, but does not fully document how the year was established or how each image maps to the final name fields.
What was reviewed—and what was not run
The existing text extraction of the four-page author PDF was read, along with madx.html and its-a-fly.html as layout references. Public source pages were fetched as text for contextual corroboration. No supplied program, script, lab, or HTML was executed or opened in a browser. The original challenge images were not available as standalone assets and were not independently compared.
What a complete solve should establish
Describe visible features before assigning them a building name.
Use the UFO/pyramid connection to generate candidates, not to prove a location.
Explain why both photographs fit the same campus and their respective buildings.
Find a source for the photo date, distinguishing capture from upload and construction dates.
Preserve the exact answer format and identify which parts are author-reported.
The central habit
Keep observation, hypothesis, corroboration, and answer acceptance in separate columns.
The central trap
A similarly shaped roof—or a photo dated 2008 somewhere on the same campus—is not automatically the source of the challenge image.
Reveal the author-reported answer
The PDF prints this answer and says it was accepted. That acceptance was not independently reproduced here.
Reported flag · verbatim prefix casing
LUH{infosys-bengaluru-terminal-building_50-2008}
The stated instructions use lowercase luh{…}, while the reported answer uses uppercase LUH{…}. The body is lowercase in both. See the walkthrough for the field breakdown and formatting caveat.
How the clues connect
Observation & evidence ledger
Generic visual features narrow a category. Distinctive structures and relationships narrow a place. The write-up's breakthrough came from changing the search question.
All descriptions of the challenge photographs below come from the supplied text, not a fresh visual inspection. No replacement photograph is presented as a challenge original.
Picture 1, as described
Apparently unfinished structure, a gap in the roof, glass-panelled walls, and an obstruction that might be a pole.
Picture 2, as described
Very blurry interior, an unusual central structure, possibly a circular support, and dark objects that might be chairs.
Observation is not interpretation
“A roof opening” is a feature. “Under construction” is an interpretation. “A circular support” is a hypothesis about function. Preserve those distinctions: an open roof may be intentional, and a dark object may not be seating.
The author suspects the pictures share a location while showing different buildings. One appears unfinished, the other polished. That is a useful working hypothesis, but neither a shared visual style nor different apparent construction stages proves they belong to one campus.
The documented clue chain
Stage
Evidence or action
What it supports
Limit
Metadata
Author reports neither image has useful metadata. PDF p. 1.
Shift effort to visible and contextual clues.
No raw files or metadata dump to verify the claim.
Architecture
Roof gap, glass panels, possible pole, circular central feature. PDF p. 2.
A feature list for comparing candidates.
Several details are explicitly uncertain.
Reverse image search
Many similar roof structures, no clear match. PDF p. 2.
The initial search route was inconclusive.
No named engine, crops, or result log.
UFO wording
Thematic research suggests pyramids. PDF pp. 2–3.
A new architectural search term.
An association, not evidence about UFOs or a location.
Pyramid result
Author finds a similarly shaped building at Infosys. PDF p. 3.
Infosys becomes a campus candidate.
The lead is not itself a match to both original pictures.
Map comparison
Second building and apparent pole reportedly match. PDF p. 3.
Author identifies the Infosys campus in Bengaluru.
No independent image-to-map comparison in this review.
Final candidate
Year 2008 used; building-number candidates tried. PDF p. 4.
Author reports 50 and flag acceptance.
No documented derivation of the year or trial range.
Why the pyramid lead helped
A search for “glass roof building” has many plausible matches. A search for a pyramid on a corporate campus is much more constrained. Once a company and city become candidates, the search can shift from shape alone to nearby buildings, roof geometry, and interior arrangements.
This is a search pivot: change the query because the previous method stopped discriminating between candidates. It is not a reason to accept every subsequent Infosys photograph as relevant.
Use an obstruction as context
The possible pole is easy to dismiss as visual noise. The author instead uses it as a relationship clue: it may belong to the other building visible on the campus. If original images become available, compare the obstruction's position, the camera viewpoint, and adjacent structures—not just its presence.
Better comparison: “This roof opening and this neighboring structure align from this viewpoint.” Weaker comparison: “Both pictures contain glass and something round.”
What the additional research actually adds
A public Flickr page describes an “Infosys Pyramid” on the Bangalore campus and lists a capture date of 1 June 2005. This corroborates the campus lead, not the challenge's date.
A separate Flickr page uses the name “Infosys...the ‘terminal’ building” and lists 14 May 2007 as its capture date. It supports the existence of that label, not the original-image identity.
A 2018 event venue page names the Infosys Bengaluru convention centre as building 50. This supports the building number while preserving its different public name.
A Wikimedia Commons file page for Bangalore_Infosys_.JPG exposes a recorded capture timestamp in 2008. It is a date-provenance lead, not a verified match to either challenge picture.
These are contextual checks gathered for this guide. They do not replace the author's missing image sources or prove the final flag from scratch.
Solve walkthrough
Reported route, annotated
Start with what each answer field requires. Follow the author’s successful pivot, but leave undocumented details marked as unknown rather than filling them in with a plausible story.
This is a reading plan based on PDF pages 1–4, with research-method notes added. No original-image analysis, script execution, number guessing, or flag submission was performed here.
Read the requested output before searching
The format asks for five hyphen-separated fields: location, city, picture-1 building name, picture-2 building name, and photo year. Spaces should become underscores and the instructions request lowercase.
Original format · supplied write-up, p. 1
luh{Location-city-name of the building pic1-name of building pic2-year of the photo taken}
Keep a separate slot for each photograph. The template does not say both must show the same building.
Inventory visible clues without overcommitting
Record the reported glazing, roof gap, apparent obstruction, unusual central support, and possible seating. Label “under construction” and “circular building” as interpretations.
The author reports no metadata, so this route relies on architectural and contextual research. That does not mean the images have no identifying information: the scene itself can still reveal a location.
Keep: an observation list for each picture and a separate list of possible explanations. The original ZIP and image filenames are not provided in the text.
Recognize an inconclusive reverse-image search
The author finds too many similar roofs. Treat this as a failed discriminator, not proof that image search is useless.
For later practice with authorized images, try a distinctive crop or a more specific caption query. Do not interpret high similarity or result order as proof of an exact building match.
Turn the UFO wording into a testable lead
The author’s thematic research suggests a pyramid. Searching for a pyramid-shaped building produces an Infosys candidate.
Now test the practical hypothesis—“could these structures belong to an Infosys campus?”—against photographs and surrounding geometry. No belief in UFO theories is necessary.
Record: the source of the pyramid candidate, its stated campus/city, and exactly which visible feature resembles the challenge. The PDF does not preserve an exact query sequence.
Compare the campus and both building candidates
The PDF reports checking Google Maps and matching the second building and the possible pole. It concludes Infosys, Bengaluru, and describes a terminal building.
In a reproduction, retain the camera direction and compare independent features from both images. Public sources also distinguish a terminal building label from a building-50 convention centre; do not assume those names identify one structure.
Keep separate: campus identification, picture-1 name, picture-2 name, and building number. This review did not resolve their image-specific mapping from the original photographs.
Resolve the date and number with explicit provenance
The write-up tries a candidate containing 2008 and then tries building-number values. It reports that 50 was accepted. It does not give a search range, automation method, attempt count, or a source proving the year.
Prefer a source caption, original photo page, archival record, or capture metadata tied to the same image before guessing. A construction year or an unrelated campus-photo date is not the requested capture year.
The reported year is not independently solved here
Commons has a relevant campus photograph with a recorded timestamp of 26 August 2008. Without matching it to the challenge image, that date is only a corroborating lead. The author-reported answer remains 2008.
Preserve the final answer and its limits
The author prints the final flag and reports acceptance. Preserve it verbatim for reference, then document any casing or field-mapping ambiguity alongside it.
Acceptance is evidence of what the CTF checker accepted. It is not independent proof of every architectural label or of the historical date.
Break down the reported flag
The fields below follow the original template's order. They are a syntactic reading of the published answer—not an independent identification of the two images.
Template field
Published token
Evidence status
Location
infosys
Author conclusion; public campus references provide context.
City
bengaluru
Author conclusion; public sources also use “Bangalore.”
Picture-1 building name
terminal
Position in the published template; image mapping not rechecked.
Picture-2 building name
building_50
Position in the published template; public venue page names building 50 as a convention centre.
Photo year
2008
Author-reported; exact-image date provenance remains unresolved.
Reveal the final flag and lowercase-format variant
Author-reported accepted spelling
LUH{infosys-bengaluru-terminal-building_50-2008}
Lowercase variant following the stated instructions · untested
luh{infosys-bengaluru-terminal-building_50-2008}
Do not claim both versions are accepted. The PDF's instructions and reported answer disagree about the prefix; the checker’s case sensitivity is not supplied.
If a later reproduction disagrees
Too many visual candidates: search for relationships and distinctive components rather than a generic roof shape.
Right company, wrong campus: require city-specific corroboration; Infosys has multiple campuses with striking architecture.
Correct campus, uncertain building: keep both image-name fields distinct and check alternate public labels.
Photo date differs: distinguish capture date, upload date, page date, and another image of the same place.
Flag rejected despite matching names: inspect field order, hyphens, underscores, city spelling, and prefix casing. Do not silently change the historical reported answer.
Research toolkit
Inert queries & checklists
Choose the method that answers the next unknown. A tool list is less useful than knowing what a result can—and cannot—establish.
Search progressively
Start with a discriminating shape, then add the candidate company and city. Use both “Bengaluru” and “Bangalore” when searching historical material, but preserve the published bengaluru token in the answer.
Suggested queries · not the author's exact search transcript
That the page's image is the challenge original before comparison.
CTF answer acceptance
The checker accepted a particular submitted string.
Independent historical truth, alternate casing acceptance, or a complete reproducible solve.
A date-provenance example from the research
The Commons file page for Bangalore_Infosys_.JPG lists a recorded capture timestamp of 18:38, 26 August 2008. Its file-history entry is dated 19 November 2009. Those dates answer different questions.
Recorded public-source dates · no image identity claim
File: Bangalore_Infosys_.JPG
Recorded capture timestamp: 26 August 2008, 18:38
Commons file-history entry: 19 November 2009, 05:44
Challenge-image match: not established
Do not substitute an upload/history date for a capture date.
Do not transfer this timestamp to an unmatched photograph.
Metadata on a source copy can survive even when a challenge copy has been stripped. But a source timestamp becomes relevant to this puzzle only after the images have been linked, and metadata itself is not infallible.
Keep a small research log
Reusable note template · fill in, do not execute
Picture / artifact:
Visible feature:
Interpretation and uncertainty:
Candidate company / campus / building:
Source URL and date consulted:
Exact caption or claim:
Matching features:
Contradicting features:
Date type: capture / upload / publication / construction
Original-image identity established? How?
Conclusion: candidate / corroborated / unresolved
Next unknown:
No automated number guessing is included
The PDF reports trying building-number candidates. This guide does not provide a submission script, run a guessing loop, or contact a checker. If revisiting the CTF, follow its rules; use documented public building information before guessing.
Things to learn
Takeaways & careful reasoning
The strongest part of this solve is the pivot from generic image similarity to a specific campus hypothesis. The weakest part is the undocumented jump from a candidate location to exact answer fields.
No useful EXIF does not mean no location leak
Architecture, neighboring landmarks, reflections, signs, and image-source context can identify a place without GPS tags. Metadata is one evidence channel, not the whole task.
Use odd wording to broaden hypotheses, not narrow belief
The UFO wording makes the author consider pyramids. That is productive because it generates a testable architectural lead. It does not establish a real-world explanation for the building or validate UFO theories.
Know when to change the search question
Repeated look-alike roofs are a sign that the query is too broad. A meaningful pivot adds a discriminating concept—here, a pyramid and then a company/campus. Keep the earlier result as “inconclusive,” not “wrong.”
Compare relationships as well as objects
A familiar roof may appear in many places. A roof gap, central support, adjacent structure, and obstruction aligned from one viewpoint are harder to confuse. A detail that seems to block the image can help anchor its position.
Separate “same place” from “same building”
Two pictures can share a campus while showing distinct structures. The final template has separate building-name fields. Flattening them into a single label loses information and can make later recollection inaccurate.
Dates need an artifact-specific source chain
A campus photograph dated 2008 is not proof that every similar photograph was taken that year. Capture time, upload time, and building completion date must be labeled separately. A title suggesting the past is not enough to derive a year.
Record acceptance without overstating it
The author says the flag was accepted. Preserve that historical result, but do not call it a newly reproduced solve. Trying an answer value can reveal a checker token without proving a building label or timestamp independently.
Claims to retain precisely
Overstatement
More precise version
“The images contain no metadata.”
The author reports no useful metadata; no original files or dump were reviewed here.
“The UFO clue proves it is a pyramid.”
The clue suggested a pyramid search, which produced an Infosys candidate.
“Both images show Terminal Building 50.”
The template separates two name fields; public sources name building 50 as a convention centre. Original-image mapping is unresolved here.
“The source photo proves 2008.”
A relevant Commons photo records 2008; its identity with the challenge images is not established.
“The flag is verified.”
The PDF reports acceptance. No submission or independent original-image solve occurred in this review.
“Either flag-prefix case will work.”
The instructions use lowercase; the reported answer uses uppercase. Checker case sensitivity is unknown.
Privacy and sensible scope
Use public architectural material and authorized challenge images. Do not infer authorization to enter a private campus, identify people in photographs, investigate employee movements, or contact unrelated accounts. Uploading an image to a search service is a disclosure; avoid doing so with sensitive material.
For organizations sharing photographs, removing GPS metadata is helpful but incomplete. Review visible identifying details and whether publicly available source copies retain metadata or more context. This challenge concerns information discovery, not a demonstrated software vulnerability.
For a challenge author
Keep stable original-image references, captions, and provenance with the solution notes.
Document the year derivation rather than only recording the accepted value.
Explain the mapping from each image to each building-name field.
State the canonical prefix case and separator rules consistently.
Distinguish intended research from any permitted answer guessing, and document rules or limits.
Self-check
Can I separate a visible feature from a guess about its function?
Can I explain why the reverse-image search was inconclusive?
Can I explain how a thematic clue became an architectural search lead?
Can I distinguish campus, city, and the two building-name fields?
Can I explain why building 50's convention-centre label must not be silently merged with “terminal”?
Can I distinguish capture, upload, publication, and construction dates?
Can I name the unresolved image-identity, date, and prefix-casing issues?
Can I state exactly which claims are author-reported rather than independently reproduced?
Useful follow-up topics
Visual geolocation; perspective and spatial relationships; reverse-image-search limitations; archival source tracing; EXIF and camera-clock reliability; evidence ledgers; and privacy-aware image handling.
Files & source notes
Provenance & discrepancy register
The write-up supplies the solve narrative. Additional public pages supply context. Neither is a substitute for comparing the original challenge photographs.
Local material and missing artifacts
File / artifact
Role
Review status
Arshlaan_s Write-ups/Once Upon a Time - OSINT Write-up.pdf
Four-page author write-up.
Present. Direct PDF rendering unavailable; existing extracted text read instead.
field-guide/assets/pdfs/Once Upon a Time - OSINT Write-up.pdf
Another local PDF path listed in the collection.
Located; not rendered or compared byte-for-byte with the other PDF.
/tmp/opencode/labs-reference/pdfs/Once Upon a Time - OSINT Write-up.txt
Existing extraction of the write-up.
Read in full. No new extraction program was run.
export.md
Earlier session record with the same extracted narrative.
Relevant excerpt read; a provenance cross-check, not independent challenge evidence.
madx.html, its-a-fly.html
Requested design and interaction references.
Source read; left unchanged and never launched.
Original challenge ZIP and two images
Needed for independent visual and metadata analysis.
No identifiable standalone originals located. Filenames and ZIP name are absent from the extraction.
CTF checker / acceptance record
Would establish submitted spelling and result.
Not supplied or contacted. Acceptance is the author's report only.
Read the source in page order
Page 1: challenge text, format, lowercase/underscore instructions, and metadata claim.
Page 3: UFO/pyramid pivot, Infosys candidate, and reported Google Maps comparison.
Page 4:2008 candidate, reported number trials, 50, accepted flag, and summary.
Discrepancy and uncertainty register
Prefix case: lowercase luh{…} instructions versus uppercase LUH{…} reported answer. Preserve both roles; do not assert case-insensitive acceptance.
Building mapping: the two name fields produce terminal and building_50. The prose compresses this into a terminal-building/number description; it does not fully explain the image-specific mapping.
Year provenance:2008 appears in the attempted candidate, without a documented exact-image source or derivation.
Number trials:50 is reportedly accepted, but no range, script, or trial transcript is supplied. None is invented here.
Metadata: absence is author-reported. There is no original file or metadata dump to support an independent statement about every tag.
Image links: the extraction contains “Open original image source” labels, not their destinations or the image pixels. Those labels do not make the original assets available to this review.
Public research consulted on 17 November 2026
Sources are shown as inert text so the guide remains offline. Quotations below are short source facts; no public-source photograph is embedded.
Source
Observed fact
What remains unproven
Flickr, Don Courage, “Infosys Pyramid”
Caption places a pyramid on the Infosys Bangalore campus; page lists taken 1 June 2005 and uploaded 2 August 2005.
The Infosys media-resources gallery also appeared in search results with a “Bangalore Pyramid” label, but direct fetching returned HTTP 403. It was not treated as an inspected source or used to independently verify the photographs.
Read the compact source snapshot · includes the answer
These are selected passages from the existing write-up extraction, not a replacement for its full PDF. Line breaks are simplified; wording and reported answer are preserved.
Author text · selected passages from pp. 1–4
The UFO that came to earth mistook this for something else.
luh{Location-city-name of the building pic1-name of building pic2-year of the photo taken}
Note: luh{all_small_letters} and replace spaces with _ .
Neither image has any metadata, so EXIF is a dead end.
This looks like a geolocation-style OSINT challenge:
the answer has to come from what is visible in the pictures.
Both images seem to come from the same place, but they may
show different buildings. One looks like it is under
construction, while the other has a polished interior.
Reverse image search only added confusion. There are many
buildings with the same roof structure, so there was no clear match.
This confirmed the location as an Infosys campus in Bengaluru,
with the building being a terminal building.
With the location, city and building name identified, the
remaining unknown was the building number. The template was
tried with the year 2008, so only the number needed to be brute-forced:
LUH{infosys-bengaluru-terminal-building_xx-2008}
The correct value was 50, and the flag was accepted:
LUH{infosys-bengaluru-terminal-building_50-2008}
Review boundaries
Read: existing extracted write-up, relevant session-record excerpt, requested HTML sources, and contextual public pages.
Not performed: running supplied files, launching HTML in a browser, executing a lab or solver, image metadata extraction, map interaction, number guessing, or flag submission.
Not independently established: challenge-image identity, exact-image year provenance, image-to-building mapping, and checker case sensitivity.
Not embedded: original PDFs, challenge ZIP/images, public photographs, map tiles, remote fonts, or external scripts.
One self-contained HTML file. Page switching, theme, printing, and copying are local browser controls when you choose to open it. There is no challenge executor, network fetch, external asset, or submission form.