Radek Antoniuk rantoniuk

SIMULATION ONLY — NOT A REAL SECURITY INCIDENT

This document is an educational tabletop exercise set in an isolated, fictional environment called Project Lantern. It does not describe a real security incident or the compromise of any real-world project, organization, infrastructure, account, maintainer, or user.

Supply-Chain Incident After-Action and Disclosure Plan

Incident date: 2026-07-15
Severity: SEV-1 / critical software-supply-chain incident
Current status: Repository payloads contained; incident remains open pending credential, package-registry, and downstream verification
Private incident record: [INTERNAL INCIDENT TRACKER]

##Date and Time

=TIMEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " ")) + DATEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " "))

##Date

=DATEVALUE(SUBSTITUTE("{{OccurredAt}}"," at ", " "))

##Time

Notice

This script is no longer required with Docker for Mac which includes an option to run Docker at startup and doesn't use docker-machine to administer the local Docker engine.

Requirements

Docker Machine + Docker
curl
A Virtualbox-driven Docker Machine called "default" docker-machine create --driver virtualbox default (this is the default with Docker toolkit).

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

	const https = require('https');
	const url = require('url');
	const slackWebhookURL = 'https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX'; // CHANGE ME PLZ!

	exports.gceAudit = (event, callback) => {
	const msg = JSON.parse(Buffer.from(event.data.data, 'base64').toString());

	const slackRequest = https.request({
	hostname: url.parse(slackWebhookURL).hostname,
	method: 'POST',

	@servers(['web' => $user.'@'.$host,'localhost' => '127.0.0.1'])

	@setup
	// Sanity checks
	if (empty($host)) {
	exit('ERROR: $host var empty or not defined');
	}
	if (empty($user)) {
	exit('ERROR: $user var empty or not defined');
	}

	#!/bin/bash

	set -eu
	umask 0022

	if [[ $# -lt 1 ]]; then
	echo "Usage: $0 role_name [AWS ACCOUNT NUMBER]" >&2
	exit 1
	fi

	#!groovy
	docker.image('cloudbees/java-build-tools:0.0.6').inside {

	checkout([$class: 'GitSCM',
	branches: [[name: '*/master']],
	extensions: [
	/* [$class: 'UserIdentity', email: 'cleclerc@cloudbees.com', name: 'Jenkins as a Service'], */
	[$class: 'WipeWorkspace'],
	[$class: 'LocalBranch', localBranch: 'master']],
	userRemoteConfigs: [[credentialsId: 'github-credentials', url: 'https://github.com/cyrille-leclerc/my-spring-boot-app.git']]])

	#!/bin/bash

	set -eu
	shopt -s nullglob

	readonly base_dir=/var/local/docker-registry
	readonly output_dir=$(mktemp -d -t trace-images-XXXX)
	readonly jq=/tmp/jq

	readonly repository_dir=$base_dir/repositories

	#!/usr/bin/env zsh

	branch=`git rev-parse --abbrev-ref HEAD`

	git show-branch \| ack '\' \| ack -v "$branch" \| head -n1 \| sed 's/.\[\(.\)\]./\1/' \| sed 's/[\^~].*//'

	# How it works:
	# 1\| Display a textual history of all commits.
	# 2\| Ancestors of the current commit are indicated
	# by a star. Filter out everything else.