Company profile
NightTea Labs is a Taipei-based security research practice. Meet the team, review our service areas and understand how we document an authorised engagement.
Know who you are working with
The public brand is NightTea Labs. The contracting entity, registered details and named researchers should be checked against the written proposal and agreement before access is granted. Request the relevant documents at hello@fpic.us.
- Public brand
- NightTea Labs
- Name shown on this site
- NightTea Security Research LLC
- Office
- 5F, No. 22, Ln. 513, Ruiguang Rd., Neihu Dist., Taipei City 114, Taiwan
- Business enquiries
- hello@fpic.us
Written authorisation
Testing begins only after the target, permitted methods, test window and emergency contacts are agreed in writing.
Named delivery team
Ask for the names, roles and relevant qualifications of the researchers assigned to your project during the proposal stage.
Evidence and handover
The agreed deliverables and data handling arrangements belong in the engagement contract and the final report.
The people behind the research
These are the team members named in the company's original profile. The proposal for a specific engagement identifies who will be assigned to that work.
| Name / handle | Role | Specialties |
|---|---|---|
| 陳威宇 / nighttea | Founder / Security Researcher | Web security, vulnerability research, reverse engineering |
| 林俊豪 / 0xJH | Senior Researcher | Binary analysis, exploit development |
| 張雅婷 / etting | Researcher | Cryptography, protocol security analysis |
Professional certifications
| Certification | Holder |
|---|---|
| OSCP (Offensive Security Certified Professional) | 陳威宇 |
| OSCE (Offensive Security Certified Expert) | 林俊豪 |
| CISSP (Certified Information Systems Security Professional) | 張雅婷 |
| CEH (Certified Ethical Hacker) | 陳威宇 |
For a procurement review, ask us for current certificate identifiers and the qualifications of the researchers assigned to your project.
Research across software, infrastructure and AI
The exact methods and targets depend on the signed scope. Our published practice areas cover the following work.
Vulnerability research
Binary review, fuzzing and root-cause analysis for software and network-facing products, with reproducible evidence and an exploitability assessment.
AI system security
Review of prompt injection, tool permissions, retrieval boundaries and data exposure across an application's AI workflow.
Red team and response
Authorised exercises focused on detection and response, plus incident scoping and forensic timelines when an event has already occurred.
Firmware and devices
Firmware extraction, hardware interfaces and secure-boot review for embedded and connected products.
Security tooling
Custom testing harnesses, detection rules and integration work where existing tools do not cover the agreed task.
Coordinated disclosure
A documented path for reporting affected products to vendors and publishing technical detail after an appropriate coordination period.
From first discussion to final review
A prospective project begins with the target, business context and desired outcome. We then define scope and rules of engagement, agree on a written proposal and authorisation, conduct the assessment, walk through the results and plan remediation and re-testing as specified in the contract.
The proposal should make the deliverables, timing, contacts, data handling and commercial terms explicit. For urgent issues, the engagement needs an agreed escalation contact before testing begins.
Verify published work at the source
Public advisories appear in our advisory ledger when they can be disclosed. A CVE credit or case study should link to its source and have the necessary permission before it is presented as company work.
One public record currently listed is CVE-2024-31002, a Bento4 buffer overflow reported through the team's zhangteng0526 account. The entry links to the original report and the NVD record.
Request company information
For registration, qualifications, a sample report or a proposal, email hello@fpic.us. For a vulnerability report, use security@fpic.us and consult our security.txt file for the current reporting channel.