<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TECNO Security</title>
    <description>The latest articles on DEV Community by TECNO Security (@tecno-security).</description>
    <link>https://dev.to/tecno-security</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1384867%2F856ca898-c157-46ee-9776-08f5f3daf1f4.png</url>
      <title>DEV Community: TECNO Security</title>
      <link>https://dev.to/tecno-security</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tecno-security"/>
    <language>en</language>
    <item>
      <title>Security Vulnerability in Hidden Parameters: IDOR Attack on Mighty App Payment Page</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Fri, 09 May 2025 08:30:25 +0000</pubDate>
      <link>https://dev.to/tecno-security/security-vulnerability-in-hidden-parameters-idor-attack-on-mighty-app-payment-page-51k0</link>
      <guid>https://dev.to/tecno-security/security-vulnerability-in-hidden-parameters-idor-attack-on-mighty-app-payment-page-51k0</guid>
      <description>&lt;p&gt;Today, Rashedul from Bangladesh will share an IDOR vulnerability found on the Bxxxxxxx Web App. The impact of that issue was, it prevented victims from running music promotion campaigns that may lead to direct revenue loss of Bxxxxxxx. &lt;/p&gt;

&lt;p&gt;Here You’ll see how an IDOR can directly affect business. &lt;br&gt;
● IDOR Overview&lt;br&gt;
● Vulnerability Discovery Process&lt;br&gt;
● Vulnerability Impacts&lt;br&gt;
● Mitigation Steps&lt;br&gt;
● Best Practices for Developers&lt;br&gt;
● Tip for Hackers&lt;/p&gt;

&lt;p&gt;As a bonus, He’ll share a tool for the automation of this task for a bigger project/web application.&lt;br&gt;
● About the Burp Suite App Store&lt;br&gt;
● Installation Process&lt;br&gt;
● How the Tool Works&lt;br&gt;
● Configuring the Tool&lt;/p&gt;

&lt;p&gt;Click here to know more details: &lt;a href="https://security.tecno.com/SRC/blogdetail/418?lang=en_US" rel="noopener noreferrer"&gt;Security Vulnerability in Hidden Parameters: IDOR Attack on Mighty App Payment Page&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>writing</category>
    </item>
    <item>
      <title>[Vulnerability Campaign] Protect TECNO devices</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Mon, 21 Apr 2025 06:49:43 +0000</pubDate>
      <link>https://dev.to/tecno-security/vulnerability-campaign-protect-tecno-devices-888</link>
      <guid>https://dev.to/tecno-security/vulnerability-campaign-protect-tecno-devices-888</guid>
      <description>&lt;p&gt;Are you a white hat who is good at finding Android phone security vulnerabilities?&lt;/p&gt;

&lt;p&gt;Submit valid critical &amp;amp; high-risk ones, and the reward will be doubled!&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Activity time:&lt;/strong&gt; April 20 to May 31, 2025&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Activity Reward:&lt;/strong&gt; Double bonus for device security vulnerabilities&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Submission channel:&lt;/strong&gt; &lt;a href="https://security.tecno.com/SRC/bugSubmit" rel="noopener noreferrer"&gt;Submit your reports!&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Rule description:&lt;/strong&gt; &lt;a href="https://security.tecno.com/SRC/blogdetail/241?lang=en_US" rel="noopener noreferrer"&gt;Divice rules&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;Come and challenge us. Your submission may be a big "surprise".&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>testing</category>
    </item>
    <item>
      <title>(Ⅱ)【Report Review】2024 OWASP Mobile Top 10 Risks</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Fri, 11 Apr 2025 08:34:19 +0000</pubDate>
      <link>https://dev.to/tecno-security/iireport-review-2024-owasp-mobile-top-10-risks-34g9</link>
      <guid>https://dev.to/tecno-security/iireport-review-2024-owasp-mobile-top-10-risks-34g9</guid>
      <description>&lt;p&gt;In the previous article,&lt;a href="https://security.tecno.com/SRC/blogdetail/405?lang=en_US" rel="noopener noreferrer"&gt; (Ⅰ)【Report Review】2024 OWASP Mobile Top 10 Risks&lt;/a&gt;, we provided a detailed analysis of the first five security risks: Improper Credential Usage, Inadequate Supply Chain Security, Insecure Authentication/Authorization, Insufficient Input/Output Validation, and Insecure Communication.&lt;/p&gt;

&lt;p&gt;Today, let us dive into the remaining five critical security risks: Insufficient Privacy Controls, Inadequate Binary Protections, Misconfiguration Issues, Insecure Data Storage, and Weak Cryptographic Measures. By understanding these risks, we can better protect mobile applications and enhance overall security practices.&lt;/p&gt;

&lt;p&gt;Click here to know the details: &lt;a href="https://security.tecno.com/SRC/blogdetail/407?lang=en_US" rel="noopener noreferrer"&gt;(Ⅱ)【Report Review】2024 OWASP Mobile Top 10 Risks&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
    </item>
    <item>
      <title>(Ⅰ)【Report Review】2024 OWASP Mobile Top 10 Risks</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Thu, 10 Apr 2025 07:49:15 +0000</pubDate>
      <link>https://dev.to/tecno-security/ireport-review-2024-owasp-mobile-top-10-risks-5462</link>
      <guid>https://dev.to/tecno-security/ireport-review-2024-owasp-mobile-top-10-risks-5462</guid>
      <description>&lt;p&gt;The rapid expansion of mobile applications has brought about security risks such as data collection violations, malicious data misuse, unlawful data acquisition, and malicious data dissemination. These security risks are prevalent in the current mainstream mobile application systems, posing serious threats to data security and personal information safety.&lt;/p&gt;

&lt;p&gt;In 2024, OWASP (Open Web Application Security Project) released the latest version of its top ten security risks report for mobile application systems, marking the first update on mobile application system-related risks since 2016. This update places a particular emphasis on risks related to supply chain security and privacy protection. &lt;/p&gt;

&lt;p&gt;The report covers ten major risks in mobile application systems and provides detailed descriptions of security weaknesses, business impacts, risk scenarios, and preventive measures, offering a comprehensive security reference for mobile application developers and security professionals. Let's delve into the relevant risks and protective measures together.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;M1: Improper Credential Usage&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;M2: Inadequate Supply Chain Security&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;M3: Insecure Authentication/Authorization&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;M4: Insufficient Input/Output Validation&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;M5: Insecure Communication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Click here to know the details: &lt;a href="https://security.tecno.com/SRC/blogdetail/405?lang=en_US" rel="noopener noreferrer"&gt;(Ⅰ)【Report Review】2024 OWASP Mobile Top 10 Risks&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
    </item>
    <item>
      <title>(Ⅱ) Android Identity Authentication</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Wed, 26 Mar 2025 06:51:57 +0000</pubDate>
      <link>https://dev.to/tecno-security/ii-android-identity-authentication-486g</link>
      <guid>https://dev.to/tecno-security/ii-android-identity-authentication-486g</guid>
      <description>&lt;p&gt;In the previous sharing, we learned about some misunderstandings and security risks related to identity authentication and also gained some understanding of blind spots related to Activity identity authentication and Broadcast identity authentication. Click to read the details: "&lt;a href="https://security.tecno.com/SRC/blogdetail/399?lang=en_US" rel="noopener noreferrer"&gt;(Ⅰ) Android Identity Authentication: A Cat and Mouse Game between Developers and Hackers&lt;/a&gt;"&lt;/p&gt;

&lt;p&gt;This article will focus on identity authentication-related topics within applications and system services, while also proposing some effective security practices. These practices aim to help developers resist related security risks during the development process and enhance the security of product services.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. The "Trap" of Service Identity Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;5.1 Cat-and-Mouse Game: How Hackers Attack Services&lt;/li&gt;
&lt;li&gt;5.2 Barking Up the Wrong Tree: Authentication on the Client Side&lt;/li&gt;
&lt;li&gt;5.3 Carving a Boat to Find a Sword: Authentication in onBind&lt;/li&gt;
&lt;li&gt;5.4 Setting Your Own Trap: Misuse of clearCallingIdentity&lt;/li&gt;
&lt;li&gt;5.5 Passing Off as Genuine: Package Name Forgery&lt;/li&gt;
&lt;li&gt;5.6 Going in the Wrong Direction: Misuse of Authentication APIs&lt;/li&gt;
&lt;li&gt;5.7 Self-Destruction: Missing Permissions for Special Interfaces&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;6. Summary: How to Win in This Cat-and-Mouse Game&lt;/strong&gt;&lt;br&gt;
① Ensure the authenticity and validity of the counterpart's identity, and beware of identity authentication "illusions" and "blind spots."&lt;br&gt;
② Authenticate all interfaces on the server side, except in special cases.&lt;br&gt;
③ Use system APIs correctly and appropriately, paying attention to special cases.&lt;br&gt;
④ Ensure permission matching in class inheritance relationships.&lt;br&gt;
⑤ Treat all inputs as untrusted; package name verification must ensure the authenticity of inputs.&lt;/p&gt;

&lt;p&gt;Click here to know the details:&lt;a href="https://security.tecno.com/SRC/blogdetail/401?lang=en_US" rel="noopener noreferrer"&gt; (Ⅱ) Android Identity Authentication: A Game of Cat and Mouse between Developers and "Hackers"&lt;br&gt;
&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>bugbounty</category>
      <category>development</category>
    </item>
    <item>
      <title>(Ⅰ) Android Identity Authentication: A Game of Cat and Mouse between Developers and "Hackers"</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Mon, 24 Mar 2025 07:11:04 +0000</pubDate>
      <link>https://dev.to/tecno-security/i-android-identity-authentication-a-game-of-cat-and-mouse-between-developers-and-hackers-2a88</link>
      <guid>https://dev.to/tecno-security/i-android-identity-authentication-a-game-of-cat-and-mouse-between-developers-and-hackers-2a88</guid>
      <description>&lt;p&gt;In Android development, caller identity authentication is like a cat-and-mouse game between developers and "black hats." Developers play the role of the "cat," trying every means to protect the "cheese," while "hackers" are the "mice," constantly searching for vulnerabilities to breach defenses. &lt;/p&gt;

&lt;p&gt;A slight oversight can allow the "mice" to slip in silently, steal data, escalate privileges, or even crash the system. This article will explore strategies in this cat-and-mouse game—how to perform reasonable and correct identity authentication. We will start with some real-world cases to help everyone recognize and understand some misconceptions about identity calls, reducing the security risks associated with improper operations and leaving the "mice" with nowhere to hide.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Common Hazards: Crises Behind the Defense Line&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. The "Illusion" of Activity Identity Authentication&lt;/strong&gt;&lt;br&gt;
3.1 Accurate Targeting: Using Reflection on mReferrer to Obtain Caller Package Name&lt;br&gt;
3.2 Accurate Targeting: Using Reflection on getLaunchedFromPackage to Obtain Caller Package Name&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. The "Blind Spot" of Broadcast Identity Authentication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Click here to know more details: &lt;a href="https://security.tecno.com/SRC/blogdetail/399?lang=en_US" rel="noopener noreferrer"&gt;https://security.tecno.com/SRC/blogdetail/399?lang=en_US&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>writing</category>
      <category>cybersecurity</category>
    </item>
    <item>
      <title>CVE Exclusive Activity</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Wed, 19 Mar 2025 02:18:39 +0000</pubDate>
      <link>https://dev.to/tecno-security/cve-exclusive-activity-2895</link>
      <guid>https://dev.to/tecno-security/cve-exclusive-activity-2895</guid>
      <description>&lt;p&gt;On March 19th, 2025, TECNO Security Response Center officially obtained authorization from the CVE program and became the first anniversary of the CVE Numbering Agency (CNA). In this year, we issued 12 CVE vulnerability numbers. Today, let's review these CVE reports together and start our exclusive anniversary activity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Activity Rewards:&lt;/strong&gt;&lt;br&gt;
① During the activity, submit valid mobile applications or terminal vulnerabilities of medium risk or higher that meet CVE allocation requirements to receive priority CVE allocation qualification and a CVE Honor Badge.&lt;/p&gt;

&lt;p&gt;② During the activity, each researcher can earn additional security points for their first valid report at different risk levels, as follows:&lt;br&gt;
&lt;strong&gt;● First valid low-risk vulnerability report:&lt;/strong&gt; 200 security credits&lt;br&gt;
&lt;strong&gt;● First valid medium-risk vulnerability report:&lt;/strong&gt; 500 security credits&lt;br&gt;
&lt;strong&gt;● First valid high-risk vulnerability report:&lt;/strong&gt; 1000 security credits&lt;br&gt;
&lt;strong&gt;● First valid critical vulnerability report:&lt;/strong&gt; 1800 security credits&lt;/p&gt;

&lt;p&gt;Click here to know more about the CVE ID reports and the activity: &lt;a href="https://security.tecno.com/SRC/blogdetail/397?lang=en_US" rel="noopener noreferrer"&gt;[CVE Exclusive Activity] Celebrating the first anniversary of TECNO Security Response Center becoming CNA!&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>[Best of February - M3Di] From Forest to Code: Transformational Security Researcher Growth Notes</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Mon, 17 Mar 2025 06:40:00 +0000</pubDate>
      <link>https://dev.to/tecno-security/best-of-february-m3di-from-forest-to-code-transformational-security-researcher-growth-notes-4e9c</link>
      <guid>https://dev.to/tecno-security/best-of-february-m3di-from-forest-to-code-transformational-security-researcher-growth-notes-4e9c</guid>
      <description>&lt;p&gt;He is from Yunnan, China, and has four years of experience in security bug mining. Over the past two years, he has dedicated himself wholeheartedly to security bug research. He is a security researcher who has successfully transitioned and grown rapidly. His name is M3Di. Today, let's explore his journey in security research together.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Following Your Inner Choice: From Interests to Careers&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If we were to describe M3Di's learning and work experience in one sentence, it would probably be 'a fantastic drift from the forest to the firewall.' Why describe it this way? Because his college major was in forestry, primarily focused on the study of forests, but now he hunts for vulnerabilities in the code jungle and has become a white hat hero in the cybersecurity world.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Safeguarding Aafety Achievements: From Persistence To Communication&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Accepting Industry Challenges: From Learning to Mastery&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Click here to know more about him: &lt;a href="https://security.tecno.com/SRC/blogdetail/395?lang=en_US" rel="noopener noreferrer"&gt;[Best of February - M3Di] From Forest to Code: Transformational Security Researcher Growth Notes&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>bug</category>
      <category>bounty</category>
    </item>
    <item>
      <title>Secure Coding Practices for TEE Applications: A Guide for CA and TA Developers</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Mon, 10 Mar 2025 06:12:16 +0000</pubDate>
      <link>https://dev.to/tecno-security/secure-coding-practices-for-tee-applications-a-guide-for-ca-and-ta-developers-2dj4</link>
      <guid>https://dev.to/tecno-security/secure-coding-practices-for-tee-applications-a-guide-for-ca-and-ta-developers-2dj4</guid>
      <description>&lt;p&gt;Trusted Execution Environments (TEEs) have become an essential component in modern secure computing architectures. TEEs provide a isolated and secure area within a device's processor, offering a higher level of security for sensitive operations and data storage. As developers working on Client Applications (CAs) in the normal world and Trusted Applications (TAs) in the secure world, it's crucial to understand and implement robust security practices.&lt;/p&gt;

&lt;p&gt;This article aims to guide developers through the intricacies of secure coding for TEE applications, focusing on best practices, common vulnerabilities, and effective mitigation strategies.&lt;/p&gt;

&lt;p&gt;Article difficulty: ⭐⭐⭐&lt;br&gt;
Chapter content preview ↓↓↓&lt;br&gt;
&lt;strong&gt;2. Secure Coding Practices for Trusted Applications (TAs)&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;3. Common Vulnerabilities and Mitigation Strategies&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;4. Testing and Validation&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;5. Performance Considerations&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;6. Keeping Up-to-Date&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;7. Conclusion&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Click here to know the details: &lt;a href="https://security.tecno.com/SRC/blogdetail/388?lang=en_US" rel="noopener noreferrer"&gt;Secure Coding Practices for TEE Applications: A Guide for CA and TA Developers&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>writing</category>
      <category>cybersecurity</category>
      <category>java</category>
    </item>
    <item>
      <title>【Recognition】Excellent Security Researcher in January 2025 iiiiiinv</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Fri, 21 Feb 2025 03:44:04 +0000</pubDate>
      <link>https://dev.to/tecno-security/recognition-excellent-security-researcher-in-january-2025-iiiiiinv-2ha1</link>
      <guid>https://dev.to/tecno-security/recognition-excellent-security-researcher-in-january-2025-iiiiiinv-2ha1</guid>
      <description>&lt;p&gt;The monthly star of TECNO Security Response Center has been announced! In January, iiiiiinv from China won this honor. We also conducted some simple interviews with him. Below is his security research story. Let's get to know him together!&lt;/p&gt;

&lt;p&gt;iiiiiinv is from China and works primarily as a software development engineer. He has been engaged in security research for about a year, dedicating his spare time to exploring security issues and discovering vulnerabilities.&lt;/p&gt;

&lt;p&gt;This marks his third month on this platform, and he feels deeply honored to have achieved such recognition so swiftly.&lt;/p&gt;

&lt;p&gt;He possesses a wealth of insights and recommendations on security research. If you wish to delve deeper, click to read the original article.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://security.tecno.com/SRC/blogdetail/387?lang=en_US" rel="noopener noreferrer"&gt;【Recognition】Excellent Security Researcher in January 2025 → iiiiiinv&lt;/a&gt;&lt;/p&gt;

</description>
      <category>security</category>
      <category>cybersecurity</category>
      <category>bugbounty</category>
    </item>
    <item>
      <title>Beginner’s Guide: Basic Methods for Finding Android Application Vulnerabilities</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Wed, 19 Feb 2025 07:06:53 +0000</pubDate>
      <link>https://dev.to/tecno-security/beginners-guide-basic-methods-for-finding-android-application-vulnerabilities-1m0n</link>
      <guid>https://dev.to/tecno-security/beginners-guide-basic-methods-for-finding-android-application-vulnerabilities-1m0n</guid>
      <description>&lt;p&gt;Phyo WaThone Win from Myanmar shared with us a guide to common Android application vulnerabilities. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Article type:&lt;/strong&gt; Bug bounty practice&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Article difficulty:&lt;/strong&gt; ⭐⭐⭐&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chapter content preview ↓↓↓&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Summary Introduction&lt;/li&gt;
&lt;li&gt;SSL Pinning Bypass using Frida, Objection&lt;/li&gt;
&lt;li&gt;Insecure Storage for Sensitive Information&lt;/li&gt;
&lt;li&gt;Testing for Insecure Communication&lt;/li&gt;
&lt;li&gt;Finding for Hardcoded Information&lt;/li&gt;
&lt;li&gt;Testing Insecure Activities, Deep Links&lt;/li&gt;
&lt;li&gt;Firebase Database Takeover
Addendum: Popular tools name for Android penetration testing&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Everyone is welcome to learn and share:&lt;/strong&gt; &lt;a href="https://security.tecno.com/SRC/blogdetail/385?lang=en_US" rel="noopener noreferrer"&gt;Beginner’s Guide: Basic Methods for Finding Android Application Vulnerabilities&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>"Hacker of the Month" - Find Excellence</title>
      <dc:creator>TECNO Security</dc:creator>
      <pubDate>Tue, 11 Feb 2025 09:33:19 +0000</pubDate>
      <link>https://dev.to/tecno-security/hacker-of-the-month-find-excellence-2520</link>
      <guid>https://dev.to/tecno-security/hacker-of-the-month-find-excellence-2520</guid>
      <description>&lt;p&gt;To motivate and express our gratitude for the continuous support of security researchers, we now specially launch the "Hacker of the Month" columns, commending outstanding security researchers every month.&lt;/p&gt;

&lt;p&gt;After you submit a security vulnerability report, we will check it and reward you after confirming it is valid. At the same time, we will select the best researcher of each month and give him this special honor and a 500 security credits reward.&lt;/p&gt;

&lt;p&gt;Click here to submit the security reports: &lt;a href="https://security.tecno.com/SRC/bugSubmit" rel="noopener noreferrer"&gt;Submit your reports &lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the reward detail: &lt;a href="https://security.tecno.com/SRC/blogdetail/379?lang=en_US" rel="noopener noreferrer"&gt;"Hacker of the Month" -Find Excellence&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>security</category>
      <category>bugbounty</category>
    </item>
  </channel>
</rss>
