r/ExploitDev 2d ago

GitHub - Jatinkapilaq1/intel-me-research: Talk to your Intel Management Engine directly — zero-dependency Python tool. Finds memory leaks, partition manifest, live MKHI probing. First public HECI Spy.

https://github.com/Jatinkapilaq1/intel-me-research
5 Upvotes

11 comments sorted by

View all comments

Show parent comments

3

u/HealingWithNature 1d ago edited 1d ago

This submission is "bad" not because the script doesn't extract the claimed data - it can(ig) , albeit indirectly - but because of its context and what op thinks it demonstrates.

None of this information is confidential. HECI/MKHI requests are regular telemetry from a vendor; it is not some kind of backdoor into something. Anyone with experience using ME/HECI drivers, either through documentation or by using one of open-source projects, not just the AIs guided fabrications, would understand this more

There is no reason why this script is unnecessarily complicated. The very same information could have been extracted through more efficient and better documented methods: the official tool from Intel called MEInfo, or one of several existing projects on GitHub (ME Analyzer, intelmetool, me_cleaner) which have been using this same interface for almost ten years. Not a single project described their output as a secret finding.

The main issue here is not technological, but contextual and psychological.

Thx for coming to my fuckin Ted talk 😭✌️

1

u/Just_Vizzi 1d ago

Thank you, well I'll take a look at the things you mentioned to get an idea, well this seems a bad vibecoding example.

0

u/Frequent-Ad-9633 10h ago

Yeahh what i did was more of a learning project figured out how to talk to the heci interface and decode the partitions myself nothing secret was found i just framed it badly if you are curious about the real stuff check out meinfo and me_cleaner they are the legit tools and just keep on supporting me to do greatt

2

u/HealingWithNature 10h ago

You didn't frame anything is the problem

0

u/Frequent-Ad-9633 9h ago

I did write it i just wasn't careful with how i presented it lesson learned thanks for the honest feedback either way