HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cattius
opcodetester
C2020–2020
cattius / opcodetester

opcodetester

Tool for automated testing and analysis of Intel x86-64 undocumented instructions in user mode and in the kernel

3Distinct people
4Mentions
0Explicit recommenders
48GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Tool for automated testing and analysis of Intel x86-64 undocumented instructions in user mode and in the kernel

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour4 dated mentions

Observed mentions: 2020-03-08 11:37:50 UTC to 2020-03-08 21:37:54 UTC.

0122020-03-08 11:00:00 UTC to 2020-03-08 12:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMar 8, 11:002020-03-08 12:00:00 UTC to 2020-03-08 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 13:00:00 UTC to 2020-03-08 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 14:00:00 UTC to 2020-03-08 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 15:00:00 UTC to 2020-03-08 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 16:00:00 UTC to 2020-03-08 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 8, 16:002020-03-08 17:00:00 UTC to 2020-03-08 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-03-08 18:00:00 UTC to 2020-03-08 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 19:00:00 UTC to 2020-03-08 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 20:00:00 UTC to 2020-03-08 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-08 21:00:00 UTC to 2020-03-08 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 8, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 8, 11:002020-03-08 11:00:00 UTC2020-03-08 12:00:00 UTC202
Mar 8, 12:002020-03-08 12:00:00 UTC2020-03-08 13:00:00 UTC000
Mar 8, 13:002020-03-08 13:00:00 UTC2020-03-08 14:00:00 UTC000
Mar 8, 14:002020-03-08 14:00:00 UTC2020-03-08 15:00:00 UTC000
Mar 8, 15:002020-03-08 15:00:00 UTC2020-03-08 16:00:00 UTC000
Mar 8, 16:002020-03-08 16:00:00 UTC2020-03-08 17:00:00 UTC000
Mar 8, 17:002020-03-08 17:00:00 UTC2020-03-08 18:00:00 UTC101
Mar 8, 18:002020-03-08 18:00:00 UTC2020-03-08 19:00:00 UTC000
Mar 8, 19:002020-03-08 19:00:00 UTC2020-03-08 20:00:00 UTC000
Mar 8, 20:002020-03-08 20:00:00 UTC2020-03-08 21:00:00 UTC000
Mar 8, 21:002020-03-08 21:00:00 UTC2020-03-08 22:00:00 UTC101

What Hacker News says

4 sources
Associated GitHub repository with more information: https://github.com/cattius/opcodetester I know next to nothing about processors at this level, but I wonder if it would be possible for a skilled engineer to try to find these instructions by scrutinizing the actual physical instruction decoder on the chip and/or inspect the processor's microcode. Are these things possible to do? If they are, is it feasible to reverse engineer them?
In Undocumented CPU behavior: analyzing undocumented opcodes on Intel x86-64 (2018) [pdf]
Author here - the aim of this project was to explore exactly why such opcodes are problematic for security. Even if they're implemented with entirely innocent intentions - e.g. for debug+verification purposes - they can lead to vulnerabilities in operating systems, emulators, and hypervisors. They induce edge cases which developers can't protect against if they don't know they exist in the first place (due to the lack of any public documentation). There's a more thorough writeup of the project here: https://github.com/cattius/opcodetester/blob/master/thesis.p....
In Undocumented CPU behavior: analyzing undocumented opcodes on Intel x86-64 (2018) [pdf]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.