RPS League App
React and Node.js with Prisma; SSE for live league state. Domains: matches, auth, sync not only screens.
Software I have built and shipped: applications, APIs, defensive tooling, labs, and research artifacts. Each entry focuses on architecture and responsibility not only a feature list.
End-user or multi-service software with UI, API layer, and persistence.
React and Node.js with Prisma; SSE for live league state. Domains: matches, auth, sync not only screens.
Integration layers and scripts where requests, responses, and errors are the product.
Utilities for composing API calls, handling failures, and making outputs reusable from the shell or other tools.
Defensive utilities and host-focused helpers interfaces, config, and deliberate scope (including what the tool does not do).
Blue-team oriented scripts and utilities; trust boundaries and safe defaults documented.
Visibility and checks around endpoint signals; pair with lab validation.
Offensive-capable lab code stays scoped to education and detection research; controls and mitigations are documented.
Pipelines, rules, and validation not a single alert screenshot.
Rule design and event flow experiments against realistic noise and attack simulation.
Elastic-focused ingest, KQL, and correlation patterns tied to collected data.
Network-layer scenarios with paired detection thinking what shows up where, and what does not.
Exercises around memory safety, privilege, and platform behavior small, verifiable scopes.
Thin clients that reduce context switching; permissions and what leaves the browser are explicit.
IP reputation lookups for triage.
Selection-based jump to Shodan context.
URL, domain, and hash lookups.
Faster Event ID context during log review.
Bug bounty PoCs, malware notes, OSINT reporting sanitized, scoped, and evidence-led.
Responsible, minimal reproducers and documentation aligned with program rules.
Heavier analysis and community-facing work that does not live in a single repo.
Comprehensive analysis of malicious behavior in files shared via Discord.
Tools used: YARA, ProcMon, capa.
Sample hash:
df46dbe66498cd0d9ea8cc62c693172943bc91ff200c06617aa1f5503dae7976
RCC.exe (PID: 3320) associated with the sample.Open-source intelligence work to identify sites and communities violating platform policies or legal norms.
Built moderation regex to filter spam, malicious links, and abusive content across multiple streams.
Example pattern (shortened for display; full pattern lives in repo/writeup):
(?i)(^(best|b\se\ss\st) (viewers|v\si\se\sw\se\sr\ss) (on|o\s))...
These rules reduced manual interventions and improved real-time enforcement of chat guidelines.