Skip to main content

Security report for yupana.finance

MadFish.Solutions · Finance · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

70/100

Risk levelMedium

0–100, higher is better. How it is calculated

Yupana.finance is an open-source, decentralized lending protocol built on the Tezos blockchain, enabling users to deposit and borrow digital assets in a permissionless and non-custodial manner. The platform is developed by MadFish.Solutions, known for the Temple wallet and QuipuSwap DEX, positioning Yupana as a pioneering DeFi solution within the Tezos ecosystem. The website provides comprehensive documentation and links to the application, emphasizing transparency and community trust through external audits and open-source code repositories. Technically, the site leverages modern web technologies including React and Gatsby, ensuring a performant and mobile-optimized user experience. Security posture is solid with HTTPS enforced and no exposed sensitive data, though improvements are recommended in security headers and incident response disclosures. Privacy compliance is addressed with clear policies, though cookie consent mechanisms are absent. Overall, Yupana.finance presents a credible and professional DeFi platform with room for enhanced security and privacy practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching yupana.finance

This scan found 23 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
52
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
68
Average
70

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Yupana.finance targets the growing decentralized finance market on the Tezos blockchain, offering lending and borrowing services that capitalize on the demand for trustless financial instruments. Its business model is based on smart contract-driven interest accrual and collateralized loans, appealing to crypto users seeking decentralized alternatives to traditional finance. The association with MadFish.Solutions and integration with popular Tezos tools strengthens its market position. Revenue streams likely include fees or interest spreads from lending activities. The platform's open-source nature and external audits enhance trust and facilitate community engagement. Partnerships and social media presence indicate active ecosystem participation, though direct contact information is limited, which is common in DeFi projects. Growth potential is tied to Tezos adoption and DeFi market expansion.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and no visible sensitive data leaks. The use of smart contracts for non-custodial lending reduces centralized risk. However, the absence of security headers such as Content-Security-Policy and lack of explicit security policies or incident response contacts represent gaps. No vulnerability disclosure or security.txt files were found, limiting transparency for security researchers. Cookie consent mechanisms are missing despite cookie policy presence, which may impact privacy compliance. Overall, the platform shows good security fundamentals but should enhance transparency and technical controls to align with best practices and regulatory expectations.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish a dedicated security policy and provide clear incident response contact information to improve transparency and trust.
  3. Add a cookie consent banner or mechanism to comply with privacy regulations and user expectations.
  4. Create a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features to improve inclusivity and compliance with accessibility standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MadFish.Solutions
Description
Yupana is an open-source, decentralized lending platform built to securely borrow and lend digital assets via smart contracts that provides the Tezos community with the benefits of decentralized financial applications.
Key services
Crypto asset lending, Crypto asset borrowing, Interest earning on deposits
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, JavaScript, CSS
Frameworks
Gatsby
Platforms
Tezos blockchain
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Non-custodial smart contract based lending
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a professional, open-source DeFi lending platform on Tezos blockchain.
  2. No direct contact emails or phone numbers found on the site.
  3. Privacy, cookie, and terms policies are present and linked externally via GitBook.
  4. No explicit security policy or incident response contacts found.
  5. No security.txt or vulnerability disclosure page detected.
  6. Site uses modern web technologies and is mobile optimized.
  7. Google Analytics is used for tracking; no cookie consent banner detected.
  8. No suspicious or malicious content detected.
  9. WHOIS data is limited but consistent with privacy protection norms in crypto space.
Technical notes

Notes

The website is built using React and Gatsby, indicating a modern, static-site generation approach that supports fast loading and SEO optimization. The use of Google Analytics and Google Tag Manager enables user behavior tracking, though privacy controls could be improved. The site is mobile optimized with responsive design and good navigation clarity. No CMS was detected, suggesting a custom or static content approach. Hosting details are not explicit but the site loads quickly and reliably. Technical debt appears low, but adding security headers and accessibility improvements would strengthen the technical foundation. Overall, the infrastructure supports a professional and user-friendly experience suitable for a DeFi platform.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with yupana.finance. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review yupana.finance.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.