Agentic Testari Sentinel Hub · FriendlyAI agentictestari.com

Confidential

L3 MAX Public-max · non-destructive

Public surface assessment — NoA Ignite

Apex marketing cleaner than product hosts. True L3: Swagger on BFM prod, unauthenticated metrics API, SPA token/source-map class plus related brand tools. HIGH 5 · MEDIUM 4.

Target noaignite.com Date 2026-07-29 RoE public-max · non-destructive Engagement eng_noaignite_l3_1358

HIGH

MEDIUM

INFO

—

Executive summary

Why act now

These findings are not theoretical: they are public surfaces a human or a hacker agent can consume today. Each card has proof links, impact, owner, fix, and validation — so the team takes risk seriously and acts.

Each finding includes: problem, where (clickable link), attacker/agent impact, owner, PoC (read-only), how to fix, and how to validate.

Apex marketing cleaner than product hosts. True L3: Swagger on BFM prod, unauthenticated metrics API, SPA token/source-map class plus related brand tools. HIGH 5 · MEDIUM 4.

Stack in this run

Component	Used	Note
ParviClaw Core + AWP	YES (lab)	full pack on engagement
ParviSight browser	partial	HTTP walk / agentic
PayBotFin Witness live	as engaged	honest scope in annex

Findings

Each finding includes: problem, where (clickable link), attacker/agent impact, owner, PoC (read-only), how to fix, and how to validate.

NO-H1

Public Swagger UI on BFM prod API

HIGH

The problem

https://bfm-app-prod.azurewebsites.net/swagger/index.html returns 200 Swagger UI for the production “Burn for Money” API. last_reprobe=2026-07-31.

Public engineering/tooling yields free recon (versions, configs, APIs).

Where

https://bfm-app-prod.azurewebsites.net/swagger/index.html · https://bfm-app-prod.azurewebsites.net

What an attacker or hacker agent can do

Human: Public eng surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Probe APIs/health in loops; correlate versions with CVEs.
If invasive/destructive: Source/secrets/CI risk if auth weak later. L3 only proves public exposure.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://bfm-app-prod.azurewebsites.net/swagger/index.html'

How to fix

Remove from public DNS or require VPN/SSO; disable anonymous APIs; re-test from the public internet on noaignite.com.

How to validate the fix

Remove from public DNS or require VPN/SSO; disable anonymous APIs; re-test from the public internet on noaignite.com.

NO-H2

Unauthenticated org metrics API

HIGH

The problem

https://noaignite.com/ — What / evidence: GET /public/api/totalnumbers → 200 live JSON (distance/time/money/engagement). Fix: Auth or aggregate only last_reprobe=2026-07-31.

Public metrics leak ops data useful for targeting.

Where

https://noaignite.com/ · https://noaignite.com

What an attacker or hacker agent can do

Human: Public metrics surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/'

How to fix

Require auth on metrics/Grafana/Prometheus or put behind VPN; never expose raw metrics publicly.

How to validate the fix

Require auth on metrics/Grafana/Prometheus or put behind VPN; never expose raw metrics publicly.

NO-H3

BFM SPA + historical Contentful preview token risk

HIGH

The problem

Client bundle https://bfm.noaignite.com/static/js/main.ef1f505e.js contains Contentful SDK init: - space: "r9sx20y0suod" - accessToken: "0cfdeec8…927fc4" (full value in bundle) - host: "preview.contentful.com" (Preview API, not delivery CDN) The matching source map (main.ef1f505e.js.map, ~8.5 MB) is also publicly downloadable, making reverse-engineering trivial. last_reprobe=2026-07-31.

Public brand surface on noaignite.com expands recon until closed.

Where

https://bfm.noaignite.com/static/js/main.ef1f505e.js · https://bfm.noaignite.com · https://preview.contentful.com

What an attacker or hacker agent can do

Human: Public edge surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://bfm.noaignite.com/static/js/main.ef1f505e.js'

How to fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

How to validate the fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

NO-H4

OIDC metadata / implicit grant surface

HIGH

The problem

https://noaignite.com/ — What / evidence: OpenID config advertised on API (deep + prior). Fix: Auth code+PKCE only last_reprobe=2026-07-31.

Public auth/federation edges expand phishing and IdP attack surface.

Where

https://noaignite.com/ · https://noaignite.com

What an attacker or hacker agent can do

Human: Public auth surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/'

How to fix

Remove non-prod auth edges from public DNS; prefer auth code+PKCE; conditional access; minimize public metadata where possible.

How to validate the fix

Remove non-prod auth edges from public DNS; prefer auth code+PKCE; conditional access; minimize public metadata where possible.

NO-H5

deskreservation public

HIGH

The problem

GET https://bfm-app-prod.azurewebsites.net/.well-known/openid-configuration → 200** JSON documenting issuer, authorization/userinfo endpoints, JWKS URI, grant types (implicit supported). last_reprobe=2026-07-31.

Public auth/federation edges expand phishing and IdP attack surface.

Where

https://bfm-app-prod.azurewebsites.net/.well-known/openid-configuration · https://bfm-app-prod.azurewebsites.net

What an attacker or hacker agent can do

Human: Public auth surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://bfm-app-prod.azurewebsites.net/.well-known/openid-configuration'

How to fix

Remove non-prod auth edges from public DNS; prefer auth code+PKCE; conditional access; minimize public metadata where possible.

How to validate the fix

Remove non-prod auth edges from public DNS; prefer auth code+PKCE; conditional access; minimize public metadata where possible.

NO-M1

test.noaignite.com Netlify public

MEDIUM

The problem

test.noaignite.com Netlify public (surface: https://noaignite.com/). last_reprobe=2026-07-31.

Public brand surface on noaignite.com expands recon until closed.

Where

https://noaignite.com/ · https://test.noaignite.com · https://noaignite.com

What an attacker or hacker agent can do

Human: Public edge surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/'

How to fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

How to validate the fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

NO-M2

retailor 401 public edge

MEDIUM

The problem

auth-required but internet-reachable (surface: https://noaignite.com/). last_reprobe=2026-07-31.

Public brand surface on noaignite.com expands recon until closed.

Where

https://noaignite.com/ · https://noaignite.com

What an attacker or hacker agent can do

Human: Public edge surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/'

How to fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

How to validate the fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

NO-M3

Thin marketing CSP / missing nosniff samples

MEDIUM

The problem

Thin marketing CSP / missing nosniff samples (surface: https://noaignite.com/). last_reprobe=2026-07-31.

Weak browser security headers increase impact of XSS/clickjacking/MITM.

Where

https://noaignite.com/ · https://noaignite.com

What an attacker or hacker agent can do

Human: Public headers surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/' | egrep -i 'strict-transport|content-security|x-frame|x-content'

How to fix

Add/tighten HSTS, CSP, XFO, nosniff, Referrer-Policy, Permissions-Policy on https://noaignite.com/.

How to validate the fix

Add/tighten HSTS, CSP, XFO, nosniff, Referrer-Policy, Permissions-Policy on https://noaignite.com/.

NO-M4

Careers multi-country hosts

MEDIUM

The problem

Careers multi-country hosts (surface: https://noaignite.com/). last_reprobe=2026-07-31.

Public brand surface on noaignite.com expands recon until closed.

Where

https://noaignite.com/ · https://noaignite.com

What an attacker or hacker agent can do

Human: Public edge surface on noaignite.com expands attacker recon.
Agent (LLM+tools): Keep surface in continuous recon.
If invasive/destructive: Escalate if second bug/credential. L3 public-max is read-only.

Who owns it

NoA Ignite — security / product / infrastructure (confirm internal owner)

PoC (proof — does not fix)

Read-only. Does not change the system.

curl -sSI 'https://noaignite.com/'

How to fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

How to validate the fix

Remove unnecessary public hosts on noaignite.com DNS or enforce strong auth/WAF; re-test from internet.

Evidence annexes (AWP + Core)

Real pack from L3 max retest 2026-07-31 (public-max, non-destructive). Each file has a caption. Links open the artifact.

1) awp-receipt.json — AWP crypto

What it is: signed Agent Witness Protocol receipt (offline-verifiable).
What it proves: integrity of our test/engagement log.
What it is NOT: not alone proof of the bug on your host (that is each finding’s PoC).
→ download awp-receipt.json

2) leaves.jsonl — engagement diary

What it is: append-only leaves (scope, probes seal, catalog, quality, seal).
What it proves: timeline of this retest run.
→ download leaves.jsonl · leaf-chain.txt (PASS)

3) retest-raw.json — HTTP probes

What it is: status/headers/samples from public-max probes.
What it proves: what the internet saw during the run.
→ download retest-raw.json

4) agentic-walk.json — surface map

What it is: multi-page walk summary (URLs, sizes, forms).
→ download agentic-walk.json · core-export.json

5) folder

→ open full evidence folder · engagement eng_noaignite_l3_retest_1361 · witness_mode local_awp_dev (DEV_LAB keys — not production ceremony).

How to use / verify AWP (open-source)

Client steps

Download awp-receipt.json from the annex (or clone the evidence folder).
On any machine with Node 18+:

# from the evidence folder
npx agent-witness-protocol verify awp-receipt.json

# or with local package
node /path/to/agent-witness-protocol/bin/awp.js verify awp-receipt.json

Honest PASS meaning: the receipt’s signature, Merkle inclusion, and checkpoint check out — the test log is intact.
PASS does NOT mean: your production bug is fixed, or that PayBotFin live network witness was used (this pack is local_awp_dev / DEV_LAB unless noted).

PayBotFin Witness: live network emit is optional and engagement-scoped. If not listed above as network_emit, do not claim live PayBot verification for this run.

Remediation order for the team

Close HIGH public exposures first (auth / VPN / DNS / policy).
Fix MEDIUM headers, mail policy, and non-prod exposure.
Re-test every PoC from the public internet until closed.
Archive AWP/evidence pack for audit and retest baseline.