am0nsec/HellsGate
Original C Implementation of the Hell's Gate VX Technique observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2283
- days_rel: n/a
- days_push: 1892
- n_releases_24m: 0
Adoption not part of the score
1220 stars · 138 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
The original C implementation of the Hell's Gate technique, which resolves Windows system call numbers at runtime to invoke NT APIs directly. It is a reference implementation accompanying a VXUG research paper on evading security monitoring.
Use cases
- resolve syscall numbers dynamically in windows
- bypass edr api hooking for research
- direct syscalls in c for red team tooling
- learn how hells gate technique works
- study windows ntdll syscall resolution
When to choose
- you are researching offensive security techniques or EDR evasion on Windows
- you need a minimal reference implementation of runtime syscall resolution in C
When to avoid
- you need a supported, licensed library for production software
- you are building defensive tooling or benign Windows applications
- you need a maintained project with active development or releases
Facets
library · maturity maintenance
security reverse-engineering security penetration-testing windows windows cpp syscalls malware-research edr-evasion vx-technique offensive-security ntapi
1 source
- readme: https://github.com/am0nsec/HellsGate · fetched 2026-08-28 · 3ca298e33080
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| am0nsec/HellsGate | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="am0nsec/HellsGate")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem