My bet is on one of

- A sequence number being accidentally used as the private key or

- The private key being generated securely but then accidentally truncated to 8 bits (e.g. writing a single char into a zeroed buffer when you should've memcpy'd from a char*).

The sequence number idea is supported by the fact that two of the G3B private keys are consecutive numbers. I ran a quick Monte Carlo simulation and if I got it right, sampling 8 keys from [0,255] uniformly at random (as in the truncation scenario), you'd expect them to contain 2 consecutive numbers only about 18% of the time.

▲

account42 6 hours ago | parent | next [-]

All the numbers also have digits going from left to right on a keyboard. I think the manual "random" input theory is plausible.

	▲	4 hours ago \| parent \| next [-]
		[deleted]
	▲	muvlon 6 hours ago \| parent \| prev [-]
		Oh wow, that is even more damning. Only 146 out of the possible 256 keys have this property. You only have about a 1% chance to get that 8 times in a row (A little more than 1% if sampling with replacement and a little less if sampling without. You'd expect them to at least not use the exact same key twice but at this point???).

▲

Avamander 6 hours ago | parent | prev [-]

Some error code being used? FIPS mode gone wrong?