Skip to content

security: phishing domain denylist should be CDN-sourced with signed manifest #449

Description

@nanaf6203-bit

Summary

PhishingProtection keeps a static list of known phishing domains inside the bundle; freshness is hard to verify and bundling supports larger attack lists.

Affected area

src/utils/security/phishingProtection.ts

Steps to reproduce / impact

Outdated list = high false negatives. Large list = bundle bloat.

Expected behaviour

Source the list from a trusted CDN at runtime with a signed manifest, fallback to a small in-bundle denylist. Document the update cadence.

Acceptance criteria

  • CDN manifest schema documented.
  • Fallback list size shrinks.
  • Update procedure for the list explained in README.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programpriority/p2P2 — medium prioritysecuritySecurity issue or hardening opportunity

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions