Cybersecurity
Authorized web security testing, attack-surface analysis, malware logic analysis, incident-oriented investigation and remediation support.
I don't fit into a single discipline. Independent research and hands-on work across AI / LLM systems, cybersecurity, reverse engineering, software engineering, network & systems, and SDR / satellite technology—alongside original music, MIDI engineering and visual creative practice.
My work spans engineering, applied research and creative practice. I investigate unfamiliar systems, develop testable models and turn them into working solutions. The same attention to structure, experimentation and expression connects my technical and creative work.
The technologies changed over time; the operating model stayed consistent: investigate what is really happening, form a testable model, build around the actual constraints, and validate with real systems, data, signals or a creative work. The evidence differs by discipline; the attention to structure and feedback connects them.
Start from observable behavior, interfaces, signals, traffic or artifacts rather than assumptions.
Turn incomplete evidence into a compact technical model that can be tested and refined.
Implement software, automation, integration or tooling around the real constraints.
Use repeatable tests, real workloads, operational outcomes or research evidence to close the loop.
The six engineering domains trace technical projects; the two creative practices cover original compositions, hands-on music technology and visual direction. Explore selected examples and working methods below.
Authorized web security testing, attack-surface analysis, malware logic analysis, incident-oriented investigation and remediation support.
Android / JNI / native library analysis, binary interfaces, file and data-stream formats, manual structure inference, firmware logic and encryption-mechanism investigation.
Python, Java, C, C++, JavaScript and VB/VB.NET across desktop, backend, web, automation, custom data-stream decoders, monitoring dashboards and technical tooling.
Linux, Docker, IPv4/IPv6, routing, VPNs, OpenWrt, reverse proxies, network-flow handling and cross-platform integration.
RF spectrum scanning, signal-type analysis, radio reception, antenna / feed tuning, decoding pipelines, Dockerized delivery and receiver automation.
Open WebUI deployment and OpenRouter integration; separately deployed Dify recruitment Agent and native Knowledge Base/RAG experiments; Ollama local inference services, cloud/local LLM systems, speech pipelines and applied ML research.
Long-term piano improvisation, melodic sketching and original composition since school years; selected music-video releases (2014–2017), digital notation, score-to-MIDI conversion, binary-level MIDI generation and Black MIDI experiments.
Character and scene concepts, color / material / silhouette relationships, visual storytelling and AI-assisted style iteration.
Each featured project begins with a recruiter-readable summary. Technical details stay collapsed until the reader chooses to open them; the complete public project history is preserved in the archive below.
Independent Docker deployment and troubleshooting of Open WebUI, OpenRouter model integration, SSE streaming and image-request proxy testing, plus migration of external chat histories containing images.
Scope: platform deployment, integration, migration and hands-on debugging; not a custom-built WebUI platform.
Independent Dify deployment and application configuration: an Agent supporting a real recruiting workflow, a CISSP document-ingestion test using Dify’s native Knowledge Base, and Ollama model-service connectivity checks.
Scope: platform configuration, business Agent and document-ingestion experiment; not claimed as a production rollout.
Self-hosted engineering workspace for long-running technical projects, with provider-neutral model access, persistent state, recoverable runs, tools and artifacts.
This project demonstrates AI engineering as a system-design problem rather than a single API integration: models, state, tools, files, recovery and auditability are handled together.
Real-time pipeline for Japanese TV HLS playback: browser-side audio capture, VAD, GPU ASR, language checking, LLM translation and bilingual subtitle delivery.
End-to-end software engineering across browser media, networking, backend services, GPU inference, local LLMs, scheduling, isolation and graceful degradation.
Three consecutive professional roles covering web security testing, malware / binary analysis, incident-oriented investigation and technical reporting.
This is a core professional background, not a side skill: security and reverse engineering were the main focus across my formal roles from 2022 to 2025.
Windows command-line tool for identifying sensitive plaintext transmission and prohibited-domain access from mirrored enterprise network traffic.
This is a compact example of several domains meeting in one project: packet-level networking, C/C++ development, security requirements and operational auditability.
From hands-on Windows receiver troubleshooting and automation to a rebuilt Linux ground station with modular, cross-container receiving, data access, publishing and operations; complemented by independent RF experiments.
This collaboration began with remote experiments on a Windows laptop, continued through a rebuilt Linux mini-server, and evolved into independent receiving, storage, publishing and monitoring services. My collaborator had operated a mini-server before we met; he later wiped it for new research, so the subsequent Linux deployment was a fresh build rather than an incremental change to the old installation.
First learned about GK-2A reception from an experienced operator, then offered help after he encountered a TBS5520SE driver / installation problem. This opened a two-way collaboration: RF domain learning in exchange for troubleshooting and software-engineering help.
Built a multi-process one-click workflow around TSDuck capture, timed stop/restart, dump handoff, concurrent decoding, image conversion and optional HRIT → SATAID. start.vbs, Batch scripts and separate CMD sessions preserve this original Windows-first design.
The operator formatted the mini-server’s disk to pursue new research and reinstalled the OS. Remotely helped deploy the receiving environment again, adapted paths, TBS DVB frontends and processing dependencies, and turned the working Windows workflow into reusable Linux scripts / Docker services.
Moved beyond the upstream all-in-one GK-2A image. Used named Docker volumes to let GK-2A and Himawari receivers produce data independently while separate file-management, SMB/FTP and website containers consumed and presented it. A collaborator’s 4 May 2021 field post shows himawari-rx and xrit-rx folders under one browser-based file interface on a 24/7 receiver server. Preserved all-in-one compatibility and added configurable proxies, image products, templates and public-access options.
GK-2A RF / decoder ──► GK-2A receiver container ─┐
├─► Docker named volumes ─┬─► File Manager · Caddy / Filebrowser
HimawariCast ───────► Himawari receiver container ─┘ ├─► File Server · SMB / FTP
└─► Website · custom templates / latest imagery
Remote dashboard/API · optional proxy / tunnel
Later: separate goesrecv reception-health monitor
Selected milestones from the archived @tcjj3 research log; open only if you want the chronology.
Built and released cross-platform Himawari receiving automation; documented 1,789 GK-2A images received over 2021-02-05 to 02-18 and a 24/7 mini-server receiving / colouring pipeline.
Original ↗Down-converted GK-2A from 1692.140 MHz to 32.140 MHz and compared multiple SDR/input paths. Public testing on 2021-04-06 recorded: RTL-SDR + goestools worked, RTL-SDR + GNU Radio failed, while RSP1A + GNU Radio and RSP1A → RSP_TCP → GNU Radio both worked. In that setup, the failing path was the one whose inter-component handoff used UDP; the successful alternatives either accessed the SDR natively or transported the stream over TCP. The observed contrast drew attention to the UDP input boundary and downstream packet handling in that specific receiver stack; it did not establish that all UDP-based receiving systems would fail.
Original ↗Improved GK-2A signal quality from 92% to 98% by changing feeds, while testing rooftop RF placement, 10 m cable, Bias-Tee / DC isolation and power arrangements. Built a 1.7 GHz LHCP helix for HRPT (13 May), achieved polar-orbit HRPT reception, and began investigating X-band hardware (feed and components documented on 17 May). X-band receiving experiments remained unfinished when I relocated to Hong Kong; X-band reception is not claimed as a completed result.
GK-2A RF tests ↗ · HRPT feed ↗ · X-band equipment ↗Detected FY-2G at 1687.5 MHz and iterated a custom GK-2A down-converter from an ADF4351 + SPF5189 design to SAWBird+ GOES LNA + HMC213 + LMX2594, while characterizing SNR loss and heat issues.
Original ↗Expanded to a 1.5 m dish and C/L-band experiments: HimawariCast at 4148 MHz, JCSAT-2B beacon measurement, feed comparison, and investigation of 1667–1700 MHz interference attributed to nearby LTE base stations.
Original ↗Developed and operationally deployed goesrecv-lock-monitor ↗ for the rooftop GK-2A receiver. Controlled antenna-offset tests showed that large Viterbi disagreement could still coexist with normal reception while Reed-Solomon corrections remained zero; once reed_solomon_errors became non-zero, useful reception was usually already close to the FEC cliff. The original service used that stricter reception-health threshold for HTTP status telemetry, event history and e-mail alerts. In 2026.10 it was sanitized, hardened with dwell-time / hysteresis, alert cooldown and exact nanomsg framing, then released publicly.
Successfully decoded FY-2G / FY-2H with a 100×60 cm grid antenna; continued GK-2A HRIT feed / F-D tuning and raised HRIT SNR to about 3 dB.
Original ↗Demodulated FY-4A at 1697 MHz with SatDump using a 1.5 m dish and patch feed after previous demodulation attempts had failed.
Original ↗Published an early-stage NOAA APT encoding experiment using custom images, followed by a separate technical-details post; later revisions improved the image reconstruction quality.
Original ↗Connected repositories organized by architectural responsibility: receiving, automation, shared data, presentation, operations and experimental extensions.
NORECEIVE processing-only deployment, externally hosted dashboards and shared Docker-volume access by separate presentation services. The architectural work extends well beyond using an existing template.himawari-rx --file processed the same type of stream normally. File2TCP therefore kept the working file-style output path, but replaced disk replay with a named FIFO plus TCP transport so the byte stream could remain ordered while becoming streamable.--file mode already parses. The FIFO→TCP forwarding code was tested and data forwarding worked, but the modified himawari-rx input path and end-to-end satellite reception test were never completed after the original receiving environment was no longer available.xrit-rx and Himawari himawari-rx named volumes into Caddy + Filebrowser without running either RF receiver..original.tpl derivatives that are copied and rewritten at container startup. Multiple changes were also mirrored within seconds or minutes across both repos—for example the same 401/404 pages on 2021-08-27 and matching LatestImage changes on 2021-08-31 / 2021-09-01. This is therefore best treated as the template R&D / source lineage of the website container, not an unrelated UI companion.entrypoint.sh copies the stored .original.tpl files into runtime templates before applying environment-driven substitutions. In other words: the template repo is the design / experimentation lineage; this repo is the deployable, parameterized integration.reed_solomon_errors became non-zero, reception was usually already near the FEC cliff. The historical monitor therefore used a stricter RS == 0 operational-health threshold rather than merely mirroring goesrecv's ok flag. The 2026 public hardening retained that criterion while adding dwell-time / hysteresis, alert cooldown, safer credential handling, exact nanomsg framing and a systemd service example.From spectrum investigation and long-running cross-sample analysis to an inferred data model, Java decoders, order-independent UDP processing, structured output and a working dashboard.
Entered an unfamiliar technical domain, derived a testable model from incomplete and changing observations, then turned that model into a stable, working decoder and monitoring workflow.
Analyzed a proprietary encrypted-media format using predictable MP4 structure, constrained parameter ranges and iterative verification.
Constraint-based reasoning and file-format knowledge applied to reverse engineering when both implementation details and key information are incomplete.
Custom multi-component system combining a VB frontend, Java control backend, Android TTS service, sensors and local-device protocol integration.
This project predates my formal security career and shows that software development, protocol analysis and systems integration were already part of the same working pattern.
Master’s research project building a reproducible pipeline from PSG-related audio to acoustic features, weak-label alignment, Random Forest prediction and event aggregation.
First-author conference paper: A Sleep Audio Preprocessor for OSA acoustic analysis (ICICSP 2026), with the broader project used as a reproducible applied-research pipeline.
Three distinct early projects: a reusable Standard MIDI File generator for JSON scores, an assembly-driven piano / player and a Visual Basic high-density Black MIDI generator with real playback stress tests.
Scope: real binary-format implementation and high-density tests, not merely editing MIDI notes with a sequencer.
Years of private piano improvisation and musical sketching, with selected ideas developed into finished works and independently produced videos; also digital notation, arranging, audio transcription and later music-box scoring.
Music and visual work are part of my independent creative history, alongside engineering. Both disciplines have informed how I think about structure, coherence and expression.
An extensive private practice of piano improvisation and melodic sketching, with selected ideas developed into finished arrangements, public videos and later music-box compositions.
Separate engineering projects bridging symbolic music, binary file formats, assembly programming and extreme MIDI event density.
A long-running interest in turning distinct character qualities and narrative intent into recognizable visual directions.
An unfinished fictional narrative exploring causal constraints, escalating conflict and the expressive contrast between warmth and tragedy.
Engineering models, music compositions and visual styles all involve choices about components, relationships, feedback and coherence. I am exploring how creative intent can be made more explicit and transferable across media. Current research also examines coordination with less-explicit cognition; observations, methods and demonstrable outcomes will be documented as this work develops.
The selected work section is selective. This archive keeps the full public technical history available for readers who want breadth, chronology or smaller supporting projects.
Major systems, smaller prototypes, research work and early engineering projects. Patent-related work is intentionally excluded.
“Featured above” means the project has a deeper card in Selected Work. The archive itself is the complete public index.
Extensive private practice in piano improvisation and melodic sketching, with selected material developed into original arrangements and published performance videos. Digital notation, four-hand arranging, real-time VST performance/audio capture, Photoshop visuals and Corel VideoStudio production; later original music-box scoring.
Analyzed the Standard MIDI File binary layout, manually derived tick/time conversion and implemented reusable MIDI event and file-writing routines to make JSON-extracted music playable as MIDI, without using a prebuilt MIDI generation API.
Independent low-level experiment combining assembly programming, keyboard interaction and MIDI playback. Distinct from the JSON-to-MIDI converter and from the later Black MIDI generator.
Reused custom binary MIDI-writing functions to generate repeating ascending full-range Note On / Note Off sequences; produced a >100 MB MIDI file before memory exhaustion. Used vanBasCo's, TMIDI, Piano From Above, MIDITrail and BASSMIDI / VirtualMIDISynth playback workflows with SGM-family piano SoundFont settings; observed synthesis failures and abnormal sustained output.
Extracted pitches with Melodyne Editor, manually corrected and arranged the result and published a piano score from QQ Romantic Rose Garden (Rose Town) background music. Public score ↗
Docker-hosted Open WebUI, OpenRouter API access, SSE streaming, image-request proxy tests, HTTP 500 troubleshooting and external chat-history import with image messages.
Dockerized Dify and Ollama model-service connection; recruitment-support Agent; ingestion of more than ten CISSP documents through Dify's own Knowledge Base, with a roughly three-day indexing run.
Self-hosted workspace unifying projects, tasks, conversations, models, tools, files, persistent state, recoverable execution and auditable history across cloud and local model providers.
Browser-to-GPU pipeline for Japanese TV HLS audio, VAD, real-time ASR, language checking, local-LLM translation and bilingual subtitle delivery across a VM / host boundary.
Master's research pipeline covering audio segmentation, feature extraction, event alignment, Random Forest modelling, acoustic-island / episode aggregation and reproducible evaluation on about 145 PSG-related cases.
Progressed from remotely debugging a Windows receiving setup and scripting HimawariCast automation to rebuilding a Linux mini-server and modularizing GK-2A / Himawari receiving, cross-container file access, Web presentation, remote exposure and operations. External operators publicly reported using the automation.
Spectrum and signal-type analysis; TSDuck dump capture; long-running, cross-sample structure inference and iterative validation; Java decoding, out-of-order UDP reassembly, stable structured output and an operational dashboard.
VB frontend, Java control backend, Android TTS service, sensors, local-protocol reverse engineering, TTL / RS232 / RS485 integration and long-running household automation.
C / C++ tool for HTTP / DNS recognition over mirrored enterprise traffic, identifying likely plaintext-password interactions and explicitly prohibited domain connections with structured audit output.
Gateway-side Python / NetfilterQueue / Scapy tool that intercepts HTTP response traffic and rewrites mirror-domain references in redirect-related response headers using an external source→replacement mapping list. It preserves payload length by padding or truncating rewritten data, recalculates transport checksums, and manages its own iptables NFQUEUE rule for transparent deployment across downstream clients.
Static firmware analysis and logic inference used to locate the key path of a registration algorithm despite incomplete hardware access and no full dynamic-debugging environment.
Reverse engineered Android TTS JNI / native libraries, mapped key interfaces and call chains, validated invocation and used the result to integrate voice output into the smart-home system.
Used predictable MP4 structure, constrained parameter ranges and iterative verification to infer weaknesses in a proprietary media-encryption mechanism and recover encrypted video without the original password.
VB prototype (Orbitron_Track) using Orbitron satellite-state data to calculate Doppler shift and display uplink / downlink frequency offsets, with room for later antenna and radio-parameter coupling.
The core implementation was a set of modified apt-encoder* variants derived from gkbrk/apt-encoder ↗ (AGPL-3.0-or-later). The separate image-conversion / resize utilities were supporting preprocessing tools rather than the core encoder logic. The experiment extended the encoder to test custom image and general-file-to-APT-audio workflows; the linked video records an early test build, while later revisions substantially improved the reconstructed image quality. The modified source has not been publicly released.
Built question-bank, user, score, exam-session and opening-time controls; Android handled login / answering, while a Servlet-generated web admin interface and JSON backend handled management and business logic.
Course-level group experiment covering historical market-data processing, feature construction, Random Forest training and result analysis.
The formal career is security-heavy. Independent software, systems and protocol work began earlier and recurred on a project basis before and alongside formal employment.
Authorized web security testing, vulnerability reproduction, impact analysis, remediation and attack-surface review.
Reverse engineering and security analysis for abnormal activity, malware / infection investigation, internal-network security testing and incident-oriented technical support.
Malware, worm and infected-sample logic analysis; static reverse engineering; reconstruction of infection mechanisms and response guidance.
Intermittent, project-based software customization, reverse engineering, system integration, low-level interfaces and non-standard technical problem solving from adolescence, through university, and after bachelor’s graduation.
The portfolio is intentionally not optimized for jobs that require only one narrow stack for ten years.
Cross-domain engineering, applied R&D, AI systems, technical prototyping, complex integration, unusual system investigation, security / reverse-engineering adjacent roles, and teams where the problem is not fully specified in advance.
Technical breadth with working depth, rapid transfer into unfamiliar domains, and an additional creative practice in music and visual style. I turn ideas into testable systems while paying attention to the structure and experience of what those systems express.
The public page stays intentionally selective. Detailed technical material can live in repositories, papers, project pages or private discussion where disclosure is appropriate.