Secrets baked into an image
An image deleted its .npmrc after install, so the team thought the token was gone. Read the Dockerfile, image history, and config to find every secret that shipped anyway.
What you’re looking at
An image deleted its .npmrc after install, so the team thought the token was gone. Read the Dockerfile, image history, and config to find every secret that shipped anyway.
Your goal: Find every secret that shipped inside an image, even after the team deleted the file.
- Briefing
- the story: what happened and what evidence you were handed.
- Terminal
- the dark box. It is a pretend Linux shell that runs in your browser. Type a command and press Enter. Nothing you type touches a real system.
- Walkthrough
- the numbered path. Each step says what to type and what you should see. Hints open one at a time.
- Answer boxes
- under each question step. Type what you found and press Check.
Start with step 1 in the walkthrough. Every step says what to do and what you should see. The whole thing takes about 2 min to talk through.
Briefing
shop-api:1.8 is about to be published to a partner registry. Security asked you to confirm it carries no credentials.
Each Dockerfile instruction becomes a layer. Build arguments used in RUN show up in docker history, and ENV values sit in the image config for anyone who pulls it. Deleting a file in a later layer does not remove it from earlier ones.
build-02 · Container audit
Type help for the command list and objectives for your tasks. Everything runs in this browser.
Up and down arrows walk your history. Ctrl+L clears the screen. Try help, ls, and objectives.
The whole walkthrough
Every step in order, written to be read aloud: 284 words, about 2 min. It gives away every answer, so try the steps first.