T/TRFFNSEC
06

PROJECTS / BUILD → BREAK → AUTOMATE

Tools built for
the hunt.

Security tooling, experiments, research utilities, and the things I build when repeating the same manual task starts getting annoying.

PROJECTSACTIVEFOCUSSECURITYBUILDPUBLIC
01

VULNWATCH / BROWSER SECURITY TOOLING

ACTIVE DEVELOPMENTv0.2.0MANIFEST V3

TRFFN / VULNWATCH

Less tab archaeology.
More actual research.

VulnWatch is a Chrome extension for passive technology detection and known-version vulnerability intelligence.

It watches the technical signals a website already exposes, identifies supported technologies and versions, and helps connect those observations to known security advisories.

The goal is not to replace manual research. It removes the boring part: finding a library, copying the version, opening another tab, searching advisories, losing the evidence, and doing it again.

View on GitHub↗Latest release↓
VULNWATCH.UILIVE PREVIEW
VulnWatch Chrome extension interface
PASSIVE DETECTIONOPEN PROJECT ↗
02

CAPABILITIES / WHAT IT ACTUALLY DOES

Observe the signal.
Keep the evidence.

VulnWatch separates observations from conclusions. Detection, version evidence, and advisory intelligence remain visible so a researcher can decide what is actually worth investigating.

01DETECT

Technology detection

Identifies exposed CMSs, JavaScript libraries, frameworks, WordPress components, and selected server or language signals.

02VERSION

Evidence first

Shows the runtime value, generator tag, asset path, or response header behind a detected technology and version.

03INTEL

Vulnerability intelligence

Checks supported package versions against OSV and supports optional GitHub, NVD, WPScan, and ProjectDiscovery integrations.

04QUIET

Quiet by default

Strong affected-version matches can surface as badges while uncertain results stay inside the inspector instead of creating noise.

03

WORKFLOW / PASSIVE BY DESIGN

Browser signal
to research lead.

No automatic exploitation. No hidden scanner firing requests at the target. VulnWatch starts with evidence already exposed to the browser.

01
OBSERVE

Read exposed signals

DOM metadata, runtime values, asset paths, and selected response headers.

browser → evidence
02
IDENTIFY

Map technology + version

Preserve the evidence and classify how confident the version observation actually is.

evidence → component
03
CHECK

Query vulnerability intelligence

Supported exact package versions can be checked against known advisory sources.

component → advisory
04
VERIFY

Research the actual impact

A version match is a lead. Applicability and exploitability still require human validation.

lead → researcher
04

INTELLIGENCE / OPTIONAL PROVIDERS

Bring your keys.
Or don't.

Core technology detection does not require an account. VulnWatch can use additional vulnerability intelligence providers when the researcher chooses to configure them.

01OSVNO KEY
02PROJECTDISCOVERYOPTIONAL KEY
03GITHUBOPTIONAL KEY
04NVDOPTIONAL KEY
05WPSCANOPTIONAL KEY
05

NOTES / READ BEFORE PANICKING

01 / MATCH ≠ EXPLOIT

An advisory match is a lead.

A detected affected version does not automatically prove that the vulnerable function is reachable, exploitable, or eligible for a security report.

02 / PASSIVE FIRST

No automatic exploitation.

VulnWatch is built around passive browser-side observation and read-only vulnerability intelligence lookups.

03 / YOUR DATA

No VulnWatch telemetry backend.

Detection runs locally. Optional external providers receive only the information required for the lookup being requested.

SOURCE AVAILABLE / BREAK IT RESPONSIBLY

Found something
weird?

Explore VulnWatch↗Report an issue ↗