<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Coy Emerald on Medium]]></title>
        <description><![CDATA[Stories by Coy Emerald on Medium]]></description>
        <link>https://medium.com/@coyemerald?source=rss-297960842acd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E9j4NEwnaFFLuVfBbvDJcw@2x.jpeg</url>
            <title>Stories by Coy Emerald on Medium</title>
            <link>https://medium.com/@coyemerald?source=rss-297960842acd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:43:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@coyemerald/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Bypassing WhatsApp Web’s Single-Session Restriction Using an Internal Fallback Endpoint]]></title>
            <link>https://medium.com/@coyemerald/bypassing-whatsapp-webs-single-session-restriction-using-an-internal-fallback-endpoint-340ef6dace38?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/340ef6dace38</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bug-bounty-hunting]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 06:34:13 GMT</pubDate>
            <atom:updated>2026-09-03T06:51:03.681Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello World! I am <strong>Coy Emerald</strong></p><p>A Lagos-based <strong>Cybersecurity Researcher </strong>and <strong>Ethical Hacker</strong></p><p>I woke up today, 03/09/2026, with the mood of sharing one of my recent discoveries on Meta products, i.e. <strong>WhatsApp</strong></p><p>First, this may already be a public knowledge to some few people, but I still feel that someone out there may find this information useful</p><p>As you should be aware, the “<strong>writer</strong>” on the bio of all my social media profiles, including on my Facebook account with the profile link <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a>, is really not there as a joke 😂<strong>#NotHoax</strong></p><p>As a writer (that i am), I write for free, for a fee, and even for fun. That’s why, if you take a moment to review any of my public profiles, including my X account, with the profile link <a href="https://x.com/@coyemerald1"><strong>https://x.com/@coyemerald1</strong></a> you will surely read something there that will make you to laugh bi ẹ̀ni to la Molly 😂</p><p>It’s morning here in <strong>Africa, Nigeria</strong>, as of the time I’m writing this, so I say, <strong>Good morning to anyone reading this!</strong></p><p>And a quick reminder, especially to any of my fellow youths, the fresh minds, who may also be reading this piece, <strong>please avoid drug abuse</strong></p><p>Now, let me share my discovery…</p><p>If you try to open multiple WhatsApp Web sessions via <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com/</strong></a> within the same browser profile, you may encounter a message indicating that <strong>WhatsApp is open in another window. Click “Use here” to use WhatsApp in this window.</strong>, prompting you to click <strong>“Use here”</strong> to continue using WhatsApp in the current window (see the attached screenshot)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QLEQwx8HAqbvEeyGiJk_bw.png" /></figure><p>This prompt is designed to prevent <strong>multiple WhatsApp Web sessions from operating simultaneously</strong> <strong>within the same browser profile</strong>, so I thought</p><p>Anyway, using Incognito mode abi Guest mode, or a separate browser profile may also allow users to access different WhatsApp accounts on WhatsApp Web</p><p>But attempting to login to another whatsApp account through web.whatsapp.com within the same browser profile will often trigger the <strong>“Use here”</strong> prompt (the same prompt displayed in the picture attached above) And by clicking on the <strong>“Use here”</strong> option, the active session will be transferred to the new window or tab, while the previous and active session session will be terminated</p><p>You can ask anyone in my country, <strong>Nigeria</strong>, I’m a <strong>responsible hacker</strong>, mo kì í ṣe màdàrù 😂 But ní alẹ́ ọjọ́rú (wednesday), Òṣù Kẹ́tà, ọdún 2026 yìí</p><p>During an independent security research, I reported a <strong>misbehavior to the Meta Security Team</strong> regarding WhatsApp, a discovery I came across while testing the internal WhatsApp endpoint <a href="https://web-fallback.whatsapp.com/"><strong>https://web-fallback.whatsapp.com</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*jBCh8Cb_CeptIn7-jJUTSQ.png" /><figcaption>Coy Emerald</figcaption></figure><p>During my testing, I observed that this endpoint <a href="https://web-fallback.whatsapp.com/"><strong>https://web-fallback.whatsapp.com</strong></a><strong>/</strong> appeared to <strong>behave differently</strong> from the normal <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com/</strong></a> environment by showing a QR code instead of a prompt displaying “<strong>WhatsApp is open in another window. Click ‘Use here’ to use WhatsApp in this window”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbnUppBgl0uv27BIV_IMow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-tC9oEj7eimD2s8R4bjlHA.png" /></figure><p>In all honesty, none of my students at <strong>O-Range Cybersecurity Academy</strong> would be afraid of scanning (even a malicious) QR code😂</p><p>And just like I told the participants in yesterday’s cybersecurity class at <strong>23 Taiwo Akinsanya, Oshodi/Isolo, Lagos, Nigeria</strong>, the essence of learning cybersecurity is to eliminate unnecessary fear while using the internet</p><p>After all, life itself is already full of fear; so using the internet should be something we should actually enjoy!</p><p>Anyway, for those interested in learning directly from me or becoming students of our <strong>Cybersecurity/Ethical Hacking class</strong>, I can personally be contacted on WhatsApp at <strong>+2349034847995</strong> or via email at <a href="/service/mailto:security@coyemerald.com"><strong>security@coyemerald.com</strong></a></p><p>So, seeing this QR code on <a href="https://web-fallback.whatsapp.com/"><strong>https://web-fallback.whatsapp.com</strong></a> simply appeared to me as a sign that something <strong>would go wrong </strong>😂 as there was no pop-up/prompt triggering the usual <strong>“Use here”</strong> session-transfer warning or invalidating the existing session, as it normally does on <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com</strong></a><strong> </strong>within the same browser profile</p><p>I took my phone, opened my WhatsApp account registered with the phone number <strong>+2349034847995</strong>, went to the <strong>“Linked Devices”</strong> option, clicked on <strong>“Link a device,”</strong> and then scanned the QR code displayed on <a href="https://web-fallback.whatsapp.com/"><strong>https://web-fallback.whatsapp.com</strong></a></p><p>To my surprise, I was able to log in successfully to the same WhatsApp account. I logged out and repeated the same process with my other WhatsApp account, registered with my other phone number, <strong>+2347067864301 </strong>And again, the login was successful</p><p>What caught my attention, however, was that the other browser tab within the same browser profile, which already had my WhatsApp account associated with <strong>+2349034847995</strong> linked through <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com</strong></a>, remained <strong>active</strong></p><p>And everything there continued working perfectly, <strong>without the existing session being logged out</strong></p><p>In my view, this created an <strong>apparent inconsistency between the session behavior and restrictions implemented on the primary WhatsApp Web</strong> platform, <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com</strong></a></p><p>So, I responsibly reported this finding to the <strong>Meta Security Team on March 18, 2026</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*jBCh8Cb_CeptIn7-jJUTSQ.png" /><figcaption>Coy Emerald</figcaption></figure><p>And their team acknowledged my report and initially requested that I refrain from publicly disclosing the information while they reviewed and investigated the reported behavior</p><p><strong>Following several exchanges over the course of several months</strong>, the <strong>Security Team</strong> contacted me on <strong>Thursday, July 30, 2026</strong>, and concluded that the reported behavior <strong>did not constitute a security vulnerability</strong></p><figure><img alt="Coy Emerald" src="https://cdn-images-1.medium.com/max/377/1*sKBc136gPiqr7B9woUlXyw.png" /><figcaption>Coy Emerald</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*r3QhEMDE9e6WZcCJp4KZww.png" /></figure><figure><img alt="Coy Emerald" src="https://cdn-images-1.medium.com/max/405/1*ttrtO9EpZfWo9d_9Ipsb4Q.png" /><figcaption>Coy Emerald</figcaption></figure><p>I respect their decision and <strong>acknowledge that not every unexpected or inconsistent behavior necessarily represents a security vulnerability.</strong></p><p>However, I maintain my position regarding this observation that the QR-code authentication process available through this fallback endpoint <a href="https://web-fallback.whatsapp.com/"><strong>https://web-fallback.whatsapp.com</strong></a> indeed bypass the session restriction enforced on <a href="https://web.whatsapp.com/"><strong>https://web.whatsapp.com</strong></a></p><p>As it allowed two separate WhatsApp accounts to be authenticated and operated simultaneously within the same browser profile without triggering session invalidation or the usual <strong>“Use here”</strong> warning</p><p>So this behavior appears <strong>inconsistent </strong>with the restrictions and user experience implemented on the primary WhatsApp Web platform</p><p>Anyway, the Meta Security Team has reviewed the report and concluded that the behavior does not meet their criteria for a Bug Bounty Program and <strong>won’t take down this subdomain</strong></p><p>So this article is therefore intended to document one of my security research findings in <strong>2026 </strong>as this also demonstrates how different endpoints may exhibit different session-management behavior in web application</p><p>Once again, <strong>Good morning!</strong></p><p>And please, don’t forget to reach out to me if you ever require the services of a <strong>Cybersecurity Specialist</strong> abi <strong>Ethical Hacker</strong> , whether it’s for <strong>Vulnerability Assessment and Penetration Testing (VAPT)</strong> or other Cybersecurity/Ethical Hacking-related services</p><p>And I also offer <strong>practical, hands-on training in Cybersecurity and Ethical Hacking</strong> for anyone interested in building real-world skills in the field of Information Security</p><p>My contact information is:</p><p><strong>WhatsApp:</strong> <strong>+2349034847995</strong><br><strong>Email:</strong> <a href="/service/mailto:security@coyemerald.com"><strong>security@coyemerald.com</strong></a></p><p>And for more information about me and what I do, you can also visit my website: <a href="http://iam.coyemerald.com/"><strong>iam.coyemerald.com</strong></a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=340ef6dace38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How an Attacker Can Exploit the Identified Open URL Redirection Vulnerability on Facebook’s…]]></title>
            <link>https://medium.com/@coyemerald/how-an-attacker-can-exploit-the-identified-open-url-redirection-vulnerability-on-facebooks-677c6752b1cf?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/677c6752b1cf</guid>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Sat, 04 Jan 2025 05:19:36 GMT</pubDate>
            <atom:updated>2025-03-17T09:32:05.339Z</atom:updated>
            <content:encoded><![CDATA[<h3>How an Attacker Can Exploit the Identified Open <strong>URL Redirection Vulnerability </strong>on Facebook’s business portfolio account setup page</h3><p>Hello World! My name is <strong>Coy Emerald</strong>, and I’m from <strong>Lagos, Nigeria</strong>, in <strong>West Africa</strong>. This is my first security story of <strong>2025</strong>. I wish you all, especially my fellow <strong>security researchers</strong>, a happy and prosperous new year!</p><p>On the morning of <strong>January 1st, 2025</strong>, while I was updating my Facebook business page with the profile name “<a href="https://web.facebook.com/orangecybersecurities"><strong>O-range Cyber Security Services</strong></a>” , I noticed an interesting feature on my dashboard called “<strong>Invite People.</strong>” As a security researcher, I decided to test the security of this feature. To my surprise, I was able to identify an <strong>Open URL Redirection Vulnerability</strong>.</p><p>Here’s how I was able to discover it:</p><p>Facebook allows users to have a business portfolio account through this page <a href="https://business.facebook.com/select/?next="><strong>https://business.facebook.com/select/?next=</strong></a> and according to best security practices, only valid names should be allowed in the “First Name” “Last Name” and “Business Name” fields. However, I noticed that the Facebook developers <strong>forgot to properly establish a “whitelist” of allowed characters in this form</strong>, specifically the “<strong>Business Name</strong>”. This allowed me to enter a <strong>URL address</strong> instead of using a valid business name.</p><p>Keep in mind that if a form requests a “(Business)Name”, users should not be allowed to enter special characters, such as URL addresses, periods, colons, commas, backslashes, etc.</p><p>While I was on <a href="https://business.facebook.com/select/?next="><strong>Facebook’s business portfolio account setup page</strong></a>, I clicked the “<strong>Create Business</strong>” button. Instead of choosing a valid business name, I entered a URL address, “coyemerald.com”. Although Facebook clearly stated that this field, including the business name field, “<strong>cannot contain special characters</strong>” such as URL addresses, but the form surprisingly accepted my submission!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J8YGzKYJKL4RqllGzpWmgw.jpeg" /></figure><p>Now, a <strong>Facebook business portfolio account</strong> has been created with a website address (which could potentially be a malicious website). I didn’t even bother to confirm my email address.</p><p><strong>Note: This entered email address, “Patchthebug@gmail.com”, is a valid email address to reach me</strong>, and I have just used it for demonstration purpose but assuming it’s just a random email address, I simply clicked “Done” and was redirected to the dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5ZyQ9ONh-XH7UATEwimqw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f2T96ceSDyikKQic6SGCrw.jpeg" /></figure><p>After logging into the dashboard, I clicked on the created Business portfolio and noticed an option to manage its information. This allowed me to choose both the profile picture and set any name. I proceeded by uploading a profile picture, using the <strong>Facebook/Meta icon </strong>for <strong>demonstration purposes</strong>, and set the name to “<strong>Meta Business Suite</strong>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FuF5PVdRN9AqRqqJMQiJMg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2zdKNvOhmovz5wG2Vo8dpQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esHnGIkkdsvm3ZxzSLoTfQ.png" /></figure><p>After completing these steps, I identified the <strong>vulnerability</strong>, specifically an “<strong>Open URL Redirection”.</strong></p><h3>Proof of Concept (POC)</h3><p>I clicked on the “<strong>Invite People</strong>” option on the Facebook business portfolio dashboard and entered one of my email addresses — I used “securemefromhacker@gmail.com”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4fJM6-Zj20ds4QadBHvJg.jpeg" /></figure><p>Shortly after, I received an email notification from <strong>Facebook</strong> with this URL address, which was <strong>clickable</strong> and redirecting to the external URL address i.e <a href="https://coyemerald.com/">coyemerald.com </a>that I had used as the <strong>business name</strong> during the portfolio account setup process.</p><p>Also, the name “<strong>Meta Business Suite</strong>” (which I had chosen) was reflected in this email, making it even more convincing. A potential victim receiving this message would likely believe it to be authentic, thinking the redirection to the website was approved by Facebook.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OaOw8rco1OWAPJ1C3bGS5A.jpeg" /><figcaption>Profile Picture:Facebook</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*cZ475vc529nkd03x_GbvGQ.jpeg" /><figcaption>Profile Picture:Meta</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lWgM0B6it1JGm4n5lqhOSQ.png" /></figure><p>Immediately after verifying this security issue, I notified the <strong>Facebook</strong> security team through their “<strong>Meta Bug Bounty Program</strong>”, following <strong>responsible disclosure practices</strong>. And I received an acknowledgement confirming the receipt of my security report.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/734/1*SF-GlEzb__gyqh_0H-c_BA.png" /></figure><h3>Now, Let’s discuss the actual cause of this “Open URL Redirection” in this Facebook’s business portfolio</h3><p>The “Business Name” field, accessible at <a href="https://business.facebook.com/select/?next=">https://business.facebook.com/select/?next=</a>, is vulnerable to “<strong>Hyperlink Injection</strong>”. This vulnerability enables an attacker to inject URLs or web addresses containing malicious content through form parameters. Consequently, it allows interaction with the content sent in automated responses from the client’s mail server.</p><p>This identified vulnerability i.e “<strong>Hyperlink Injection” </strong>on <a href="https://business.facebook.com/"><strong>https://business.facebook.com </strong></a>enables malicious users to tamper with the content of “automated responses”. Specifically, invitation emails sent from the Facebook mail server to any Facebook user,(invited users) who are now potential victims of this vulnerability.</p><p>As the automated response is sent by the official sender (meta@facebook.com) and from Facebook/Meta, a certified entity, users receive it with a high level of trust in their inboxes. This vulnerability allows phishing or malware distribution easily under Meta’s organization name. Since Attackers can redirect anyone via email to an external domain without a redirection notice, potentially endangering Meta’s reputation as a company.</p><h3>More about Impact of this Vulnerability</h3><p>The impact of this “Open URL Redirection” vulnerability, resulting from the “Hyperlink Injection”, is significant. as It allows attackers to leverage the client’s (Facebook) mail server to distribute malicious content to third parties. This can cause substantial reputational damage and compromise the integrity of the Meta/Facebook as an organization.</p><h3>My Simple Recommendations</h3><p>To mitigate this type of vulnerability, the best security practice is to <strong>enforce proper validation of allowed characters in each form field.</strong></p><p>For instance, if the “Business Name” field on <a href="https://business.facebook.com/select/?next="><strong>https://business.facebook.com/select/?next=</strong></a> had validated input to prevent URL addresses and only allow valid names, the “Open URL Redirection” vulnerability would not have existed in this endpoint.</p><h3>My Conclusion</h3><p><strong>HyperLink Injection Vulnerability is a very simple and impactful vulnerability just like HTML Injection Vulnerability</strong></p><p>And It’s very important to be aware of these techniques as they don’t trigger any alerts on the server</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf">https://selar.co/1848uf</a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=677c6752b1cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Nigerian journalist asked me: Coy, Can one legally employ a hacker to hack someone’s social…]]></title>
            <link>https://medium.com/@coyemerald/a-nigerian-journalist-asked-me-coy-can-one-legally-employ-a-hacker-to-hack-someones-social-media-bc69b10fd6f5?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc69b10fd6f5</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Thu, 05 Sep 2024 04:31:41 GMT</pubDate>
            <atom:updated>2024-09-05T07:39:21.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Nigerian journalist asked me: Coy, Can one legally employ a hacker to hack someone’s social media account?</h3><p>Globally, there are many misconceptions and misunderstandings about <strong>hacking</strong>. <br>So I recommend checking out one of my recent articles (mentioned below) which also explains <strong>what hacking is and why it matters 👇</strong></p><p><a href="https://medium.com/@coyemerald/what-hacking-is-and-why-it-matters-b44c3ea1628">https://medium.com/@coyemerald/what-hacking-is-and-why-it-matters-b44c3ea1628</a></p><p>Nowadays, the Nigerian online space has become increasingly intriguing and confusing. Everyone quickly blames hackers for security breaches, even some individuals who have voluntarily sold their social media pages now claim that hackers have taken them over 😂</p><p>Surprisingly, many Nigerians now attribute hacking to almost all incidents, including those with no connection to cyber attacks, <strong>misusing</strong> the term &#39;hacking&#39; and fueling widespread <strong>misconceptions </strong>and<strong> creating unnecessary </strong>fear to the members of the public.</p><p>Last night, <strong>Wednesday, September 4, 2024</strong>, at approximately <strong>9:41 p.m WAT</strong></p><p>I received a WhatsApp message on my number, <strong>+2347067864301</strong>, from a Nigerian journalist asking for my opinion on <strong>theverydarkman</strong> (MR. VDM)’s recent submission regarding the late <strong>Mohbad’s</strong> (Imọlẹ) tragic case. <strong>May his soul rest in peace, and if relevant , may the Irúnmolè bring justice to those involved in his passing-</strong> Àṣẹ /!!!\</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*kjRL6MXXRfDYPPYHl5jReQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*aMSg8XyH06jlJtSRb6NgDg.jpeg" /></figure><p>I quickly watched the attached video clip even before responding to the first question “ <strong>can someone employ a hacker to hack one’s account legally</strong>”?</p><p>After I finished watching the clip and reviewing Mr. VDM’s submission, including his claim that an olorukọ́-hacker 😂 provided him with information, I realized that the details related to Instagram IP addresses presented in the video are <strong>INACCURATE because</strong></p><p>There is <strong>NO proof of finding the two suspects&#39; valid IP addresses, </strong>so the so-called &#39;proof&#39; presented in this recent video shared by MR. VDM on Mohbad’s case <strong>lacks credibility,</strong> and it’s evident that his so-called hacker demonstrated a basic <strong>misunderstanding</strong> of information gathering (<strong>OSINT)</strong></p><p>Just as I advised the <strong>Philippine National Police</strong> a few hours ago to consider additional factors</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*JOsFm5Iv7utyEM90xOfNGw.jpeg" /></figure><p>Mr. VDM should also understand that if he genuinely wants to obtain SISTER Iyabo Ojo’s valid IP address or perform any technical actions, he must first <strong>grab her hand</strong> before he can successfully grab her <strong>IP Address</strong> 😂</p><p><strong>References</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*NN4Mk_pHkW5HVDgNMG3dmA.jpeg" /><figcaption>https://check-host.net/ip-info?host=Instagram.com%2F_c33why_</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*TiSOR0yrvh6zO5Yp6RNE-g.jpeg" /><figcaption>https://check-host.net/ip-info?host=Instagram.com%2Fiyaboojofespris</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc69b10fd6f5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Nigerians and South Africans could have leveraged the recent incidents at Bolt, Uber platforms…]]></title>
            <link>https://medium.com/@coyemerald/whoever-firstly-discussed-the-issue-that-recently-happened-in-uber-and-bolt-system-and-decided-to-b58dd9a520f0?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/b58dd9a520f0</guid>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Fri, 23 Aug 2024 10:44:17 GMT</pubDate>
            <atom:updated>2024-08-23T12:57:42.645Z</atom:updated>
            <content:encoded><![CDATA[<p>Whoever first discovered the recent issue in Bolt and Uber’s systems and chose to publicly disclose it on Twitter (or wherever it was first announced) instead of reporting it to the companies directly, missed out on earning Extra Cash “Bounty ” 🤑💰</p><p>Some of you might think “mo ní fẹ owó’’ (<strong>Coy Emerald</strong> likes money) but the fact is, those who truly know me in real life understand that I genuinely need money, especially since moving to Lagos, Nigeria- my financial needs have skyrocketed, just like the recent surge in Namecheap’s prices .</p><p>Even as I write this story on <strong>Friday, August 23, 2024,</strong> I received a notification on my Twitter profile <a href="https://medium.com/u/297960842acd">Coy Emerald</a> from aṣoju &#39;<strong>awọn onile orí internet ti ìlú Èkó</strong>&#39; 🤣</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Wl2przR4Kv2HB_13rDRw7Q.jpeg" /></figure><p>Dear readers, I hope you now agree that I genuinely need money 😊</p><p>For those who may not know me well, my name is <strong>Coy Emerald</strong>.</p><p>I’m a <strong>Cyber Security Specialist</strong> from <strong>Nigeria 🇳🇬</strong> <strong>Africa</strong>, I’m passionate about <strong>breaking security, but only to protect the security</strong>, and I also focus about identifying and reporting vulnerabilities in web applications and enhancing online security for businesses and individuals.</p><p>If you want to know more about me, you can visit my LinkedIn profile at <a href="https://linkedin.com/in/coyemerald">https://linkedin.com/in/coyemerald</a> to explore some of my work, expertise, and passions in <strong>cyber security </strong>and<strong> ethical hacking</strong></p><p>A few hours ago, a Nigerian cybersecurity friend reached out to me via <strong>WhatsApp</strong> <strong>(+2347067864301</strong>) to share the gist about the recent <strong>Uber and Bolt incidents</strong>.</p><p>We both had a good laugh, 😂 and I hope this story brings a smile to the faces of my readers, just like it did for many <strong>Nigerians and South Africans</strong> through this incident .</p><p>May the love and unity between our countries continue to grow, and may peace, love, and unity prevail across Africa and the world. Amin</p><p>As a side note, for those familiar with the hackers, you’ll know that laughter is common in our things- we often find a joke in security vulnerabilities, and my contacts on WhatsApp can also bear witness that sometimes, I can simply update a status with 😂🤣</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*Us9DcHgEmy5Y68zqPcpxUg.jpeg" /></figure><p>While chatting with my researcher friend, I quickly verified the story and found it to be a hilarious trend that’s currently captivating Nigerians and South Africans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*0l2dXes8L23MOOiP_W02LQ.jpeg" /></figure><p>As a Nigerian, I couldn’t resist joining in on the fun ☺️ because as we say, &#39;one of us is all of us&#39; - n’kan tó bá tí dé bá ojú, otide ba imu nìyẹn 😆</p><p>As I pondered this trend, it suddenly reminded me of my recent experience while (penetration) <strong>testing</strong> the systems of an <strong>international company.</strong></p><p>Three days ago, on <strong>August 20, 2024, I</strong> collaborated with a <strong>security team</strong> to resolve a <strong>simple</strong> yet <strong>significant error</strong> for an <strong>international</strong> organization whose name I’m not at liberty to disclose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*p91YC19PQit1Cj_sl6TXVQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ZNmo3xQp3wQZGlW2a9Nc_w.jpeg" /></figure><p>Notably, the issue was remarkably <strong>similar</strong> to this simple issue recently plaguing Bolt and Uber</p><p>Although, I hadn’t planned to share any new experiences this year through <a href="https://medium.com/u/297960842acd">Coy Emerald</a> , following my previous encounters with AT&amp;T and HackerOne -which you can read about here</p><p><a href="https://medium.com/@coyemerald/here-is-proof-that-the-telecom-giant-company-at-t-security-research-program-maybe-a-joke-4ca2e31c302">https://medium.com/@coyemerald/here-is-proof-that-the-telecom-giant-company-at-t-security-research-program-maybe-a-joke-4ca2e31c302</a></p><p>But the recent humorous trend between Nigerians and South Africans inspired me to share my thoughts in this short story today, <strong>Friday, August 23, 2024.</strong></p><p>Keynotes:</p><p>On many platforms, you may find that you’re unable to create an account or access certain features due to country restrictions or blacklisting. This means that the company has limited or blocked access to their website or specific services for users from your region.</p><p>I’m writing to inform you that if you’ve discovered a way to bypass the registration policy without using a VPN or third-party programs like RDP or VPS, and can access the platform’s full functionality - which is normally supposed to have been restricted in your region - please <strong>consider reporting this to the affected organization</strong>.</p><p>This is particularly relevant in cases like the recently exploited feature on <strong>Bolt and Uber</strong>, where <strong>unintended access was allowed.</strong></p><p>Immediately I noticed this similar bug, I reported my discovery to the international company I was testing</p><p>Although I laughed while writing the report 😂</p><p>Fortunately, it was accepted as a valid submission and I earned &quot;<strong>extra cash</strong>&quot; $$$ beyond the bounty given to me , I was glad to have played a part in <strong>helping them improve their security.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*ZcEkXvmwQA942K-I5rAvaw.jpeg" /></figure><p>The crucial <strong>takeaway</strong> is that:</p><p>Numerous security misconfigurations in web applications with significant security implications <strong>can be easily identified</strong>, and if reported responsibly, it can earn you rewards.</p><p>Many organizations value responsible disclosure and offer a VRP</p><p>Interestingly, <strong>hacking web applications often doesn’t require complex code or exploits</strong>. Many vulnerabilities (including the HIGH, CRITICAL ones) can be identified through <strong>simple means.</strong> If you’re curious about how this is possible, consider enrolling in my B<strong>ug Bounty Hunting</strong> Course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Oc3fMsqY11X4NEsVTdfAug.jpeg" /></figure><p>As a <strong>new subscriber</strong>, you’ll get access to a 3-part <strong>live session</strong> <strong>(2 hours each</strong>) and a WhatsApp Community where I’ll guide you through the course material.</p><p>Plus, feel free to reach out to me anytime with questions or clarifications via <strong>WhatsApp or email.</strong></p><p><strong>WhatsApp: +2347067864301</strong></p><p><strong>Email: security@coyemerald.com</strong></p><p>You can purchase my bug bounty hunting course by visiting the link on the flyer or clicking the link below</p><p><a href="https://selar.co/1848uf"><strong>https://selar.co/1848uf</strong></a></p><p>Good afternoon, world! As I conclude my story, it’s <strong>Friday, August 23, 2024</strong>, at <strong>1:56 PM (WAT</strong>) here. I wish you a wonderful day, wherever you are in the world!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b58dd9a520f0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I Declined the Bounty Reward Offered by AT&T After Their Recent Massive Security Breach & Why…]]></title>
            <link>https://medium.com/@coyemerald/here-is-proof-that-the-telecom-giant-company-at-t-security-research-program-maybe-a-joke-4ca2e31c302?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ca2e31c302</guid>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Mon, 12 Aug 2024 16:56:43 GMT</pubDate>
            <atom:updated>2025-12-14T07:23:05.420Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>On Friday July 12, 2024</em>,</strong></p><p>I saw Facebook notifications through my profile <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a> about a security breach on <strong>AT&amp;T’s</strong> network, where an attacker stole call records for nearly all customers</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*iPFfVr5e6pCX2hX2PD5C8A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*XAfnVHRGKgSyZUAJDeI1HA.jpeg" /></figure><p>Interestingly, I received this news about the <strong>AT&amp;T</strong> security breach during the same period I was conducting security research on their server through the <strong>H1 platform</strong>.</p><p>Moreover, this coincided with the time they just paid me for one of the vulnerabilities I had identified in their system. The fact that they paid me for one of my discoveries when this news broke makes this coincidence even more remarkable, demonstrating the authenticity of this story and preventing any misconceptions about my motives for sharing this experience I later had with them 😆</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/481/1*wNnnAdq0wasX-uyWf9vKfg.jpeg" /></figure><p>This news caught my attention because it mirrored one of the vulnerabilities I had previously identified and reported to them- <strong>AT&amp;T on July 2, 2024</strong>,<strong> 12:05pm UTC</strong> through their <strong>H1 portal- </strong><a href="https://hackerone.com/att"><strong>https://hackerone.com/att</strong></a> which was marked as a <strong>DUPLICATE on July 3, 2024</strong>, indicating that another researcher had already reported the same issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*LlBnvFD2G-rXVi9a5G-FMg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*q5JXoA_WIaltjfjaxIPt_g.jpeg" /></figure><p>This isn’t surprising, as <strong>Bug Bounty Hunting</strong> is a <strong>first-come, first-served field, where timing is crucial </strong>😫</p><p>That’s why I always encourage my <strong>bug bounty hunting </strong>course <strong>subscribers</strong> and <strong>ethical hacking</strong> <strong>students</strong> to report vulnerabilities <strong>promptly</strong> before continuing working to escalate the identified issues.</p><p>As soon as I saw this news shared on Facebook, I delved into the article to read the full details and verified the information on AT&amp;T’s official website 👇 <a href="https://about.att.com/story/2024/addressing-illegal-download.html"><strong>https://about.att.com/story/2024/addressing-illegal-download.html</strong></a> <strong>confirming that a significant data breach had indeed occurred, exposing the call and text records of nearly all their customers.</strong></p><p>However, while reviewing this news about the security incident on AT&amp;T’s website, I noticed that it was stated there that the exposed data <strong>did not include &#39;other personally identifiable information&#39; such as customers&#39; names, timestamps, locations, voice notes, pictures, and other sensitive details</strong>.</p><p>Additionally, AT&amp;T stated that they had <strong>patched the identified issue.</strong></p><p>Given my active engagement with AT&amp;T’s security systems and the similarities between this incident and a vulnerability I had previously identified in their web application, I found this article <a href="https://about.att.com/story/2024/addressing-illegal-download.html"><strong>https://about.att.com/story/2024/addressing-illegal-download.html</strong></a> particularly interesting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*e5wAyhklOe-qW192_wzLaw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*V5QZHlr9oSrizGOojWW8PQ.jpeg" /></figure><p>At this point, I simply assumed that this security breach wasn’t exactly the same issue as the one I had reported to them, so I <strong>wanted to confirm</strong>. To do this, I logged into my HackerOne portal and reviewed the old report (the same one) that had been <strong>closed and marked as a duplicate</strong> by <strong>HackerOne</strong>.</p><p>Surprisingly, after logging into my HackerOne researcher portal, I discovered that the report I had submitted, which was previously <strong>closed</strong> and marked as a <strong>duplicate</strong>, had <strong>not</strong> been resolved.</p><p>This finding, combined with the news of the breach I came across on Facebook, which AT&amp;T has also confirmed on their website, left me with a sense of unease and suspicion that something was amiss.</p><p>As the description of the breach seems similar to the identified vulnerability, AT&amp;T has also claimed to have fixed the issues. However, I believe something is wrong. Instead of reopening the issue on HackerOne,</p><p><strong>On July 13,2024</strong>, I reached out to <strong>AT&amp;T</strong> directly concerning this <strong>UNRESOLVED issue</strong>.</p><p>I wrote to them via <strong>email</strong> at “<strong>abuse@att.com”</strong>, as I wasn’t sure how to proceed with this update through HackerOne, given their role as a middleman 😂 between researchers like myself and organizations, I also copied the same sent message to their <strong>Twitter</strong> representative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*WGP3RupGIhnF5hqE_3zMqQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*InTx0zU3TcnfUiHXzglsYA.jpeg" /></figure><p>An hour later, I received a response from AT&amp;T via their Twitter page, thanking me for bringing the issue to their attention. They directed me to check my H1 portal, where I found a message from AT&amp;T staff regarding the previously closed report.</p><p>They apologized and explained that the report had <strong>not been forwarded to them, clarifying why the issue remained unresolved.</strong></p><p>Additionally, they assigned a new H1 staff member to the case and reopened the report for review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*bzpzN-zQleKYHfedSZw8UA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*yHaVSLtx0DQjc1FDftKyCg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*kErYPBOBKJqDucYKr4y9hQ.jpeg" /></figure><p>Of course, I understand that humans are not immune to making errors. However, I find it concerning that when this report was earlier closed and marked as a duplicate, I specifically requested that <strong>H1</strong> add me to the duplicate report, but they ignored my request without providing a clear reason. Now, AT&amp;T has confirmed that <strong>the issue was never forwarded to them at all.</strong></p><p>This lack of transparency really left me extremely frustrated. I expect <strong>H1</strong> to take ownership of their mistake and offer a genuine apology. Instead, they’ve chosen to continue threatening me with account suspension, which only adds to my annoyance. In a situation where a mistake has been made, <strong>transparency</strong> and a <strong>sincere apology</strong> are the bare minimum. Further intimidation and threats are unacceptable.</p><p>Well, maybe the issue was truly reported by another researcher before me, as claimed by the H1 staff who initially reviewed the report — that AT&amp;T later confirmed that <strong>the issue was never forwarded to them at all.</strong> Nevertheless, I believe <strong>HackerOne </strong>should prioritize <strong>transparency</strong> and provide <strong>sufficient information</strong> to enable researchers like myself to <strong>verify the duplicate report’s submission</strong>, beyond simply referencing an <strong>inaccessible report ID</strong>. I don’t accept their excuse that certain information can’t be shared, as sensitive details can be redacted while still providing enough context for verification.</p><p>Of course, just as I&#39;m not the only researcher reporting on hackerone, I also work with multiple companies as an external security researcher.</p><p>Recently, I submitted a report to another organization, <strong>which was unfortunately marked as a duplicate</strong>. However, unlike the current situation, the company provided clear evidence that my submission was indeed a duplicate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*lBjgv0NiMOYeRH4WMkZlpQ.jpeg" /></figure><p><strong>Transparency</strong> is a crucial aspect of <strong>responsible disclosure policies.</strong></p><p>When ethical hackers feel cheated or misled, it can lead to greater incidents beyond imagination. Being an ethical hacker doesn’t mean being naive; we simply prioritize contributing to internet safety over causing chaos!</p><p>As for <strong>HackerOne, </strong><br>I hope they will apologize for the inconvenience and take steps to enhance their <strong>verification process for duplicate submission</strong>. Specifically, I hope they prioritize alternative methods to notify researchers when a report has already been submitted, rather than merely providing an inaccessible report ID for the duplicate version. <br>This would prevent similar situations, ensuring a more transparent and efficient reporting process for the ethical hackers.</p><p>So, fast forward to <strong>July 15, 2024</strong> I received two messages: one from <strong>HackerOne</strong> and one from <strong>AT&amp;T staff.</strong> HackerOne reported that the exposed information of their thousands of subscribers, including their personally identifiable information was due to a fault of customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*3H4PwqKHuj0lmbOBj43rRQ.jpeg" /></figure><p>This response frustrated me because it implied that a <strong>vulnerability affecting thousands of customers</strong> was the <strong>users&#39; fault,</strong> when in fact, the issue <strong>clearly originated from the source - a subdomain of the website</strong>. It’s <strong>unreasonable to shift the blame to users when the root cause lies with the ATT system or infrastructure.</strong></p><p>This led me to follow up with another email to <strong>abuse@att.com</strong>, seeking clarification on the response I received from the HackerOne staff. I <strong>wanted a clearer understanding of their position and the reasoning behind this response</strong></p><p>On <strong>July 15, 2024</strong>, I sent a follow-up email to <strong>abuse@att.com,</strong> <strong>requesting clarification on the response provided by the HackerOne staff. </strong>I also copied <strong>support@hackerone.com</strong> in the email to ensure transparency and keep them informed of the communication</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*HobMZHOSmtHJiycaQjxgvA.jpeg" /></figure><p>As I always emphasize, <strong>cybersecurity is a shared responsibility</strong>. If an individual or organization fails or refuses to remediate an issue, as a security researcher, <strong>there is no law prohibiting me from taking initiative to fix it</strong>. With a clear idea on how to address the identified vulnerability, I took proactive action on <strong>July 15,2024</strong> to remediate the issue myself, while <strong>keeping both AT&amp;T and HackerOne informed of my efforts</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*vCpC5DA36c8qPhNFCVPm9Q.jpeg" /></figure><p>On this same <strong>July 15, 2024</strong>,<br>I received an unnecessary message from <strong>HackerOne</strong>, emphasizing the need for communication within their platform. However, if the reported issue had been handled efficiently and <strong>transparently, </strong>I wouldn’t have had to contact AT&amp;T directly about the mass breach affecting millions of users.</p><p>Their response also warned against public discussion of <strong>unresolved</strong> issues, threatening my account sanctions.</p><p>So despite my responsible disclosure to <strong>AT&amp;T</strong> and only sharing the <strong>inaccessible report ID</strong> with a Twitter representative,</p><p>HackerOne still threatened to ban my account that I rarely use ?😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*4NZl6zgIp_hpMen_ycmudQ.jpeg" /></figure><p>Well, As I’ve recently shared my thoughts on this on Twitter <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></p><p>I want to emphasize that <strong>direct</strong> <strong>security reporting to affected organizations is just as valid as using platforms like HackerOne.</strong></p><p>And as an ethicalhacker, I respect reasonable rules, but I will break them if necessary to protect security. ✊</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*AoDZS7MGnNXWoUJaRKlH1Q.jpeg" /></figure><p>Meanwhile, on that same day again <strong>July 15,2024,</strong></p><p><strong>AT&amp;T staff</strong> has responded, informing me that they are <strong>actively working on formulating and implementing a fix to prevent future sites from being vulnerable to this issue</strong>. Additionally, they assured me that <strong>I would receive a duly deserved bounty for my contribution</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*o3PuhTbkUzcEeuPCOqMSUA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*r-VtFLQ01zlbgW9gWiUW9Q.png" /></figure><p>Yesterday morning, <strong>Mon Aug 12 , 2024,</strong></p><p>I informed them of my decision to close this report because they were not prioritizing it. Surprisingly, they offered me a ridiculously low amount of bounty in the evening of <strong>Mon Aug 12 , 2024.</strong></p><p>I declined the offered bounty amount <strong>due to valid reasons</strong> and proposed that it be shared among their <strong>security staff</strong> or <strong>HackerOne staff</strong> instead. As the Yoruba proverb goes, &#39;unfẹ̀ osagba mofun ọ́&#39; (meaning &#39;<strong>what they offered me doesn’t adequately compensate for my time, effort and expertise’)</strong> including unnecessary drama on this submission.</p><p>As for me, <strong>Coy Emerald</strong>, it is a matter of either rewarding me with what I deserve or choosing not to reward me at all✊</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*N5Q4HOfcd7ef-fIBgQzBag.png" /></figure><p>On <strong>August 12, 2024,</strong> I expressed my dissatisfaction with the way they are handling the reopened case, citing delayed responses and the initial lack of a bounty award</p><p>Although they later offered a bounty on this same day — <strong>August 12, 2024</strong>, but I found the bounty amount insufficient considering the issue’s severity and my efforts.</p><p>Therefore, I <strong>closed the report myself and marked is as Not Applicable</strong>, forfeiting the bounty, after informing them of my intention to share my experience with both <strong>ATT &amp; H1</strong> on my Medium page and after I have earlier shared my dissatisfaction on the offered bounty and asked them to use it to buy bread and tea 😂 for both their security team and H1 staff</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ZhgTST34mOQKqmB4mDPrXA.jpeg" /></figure><p>Dear readers, it’s been a while since I’ve shared a <strong>technical story</strong> with you through this medium page; If you find this interesting , CLAP FOR ME and don’t forget to extend your thanksgiving to both <strong>ATT &amp; H1</strong> for inspiring me to write this short story.</p><p>I wish you all well in your cyber security and ethical hacking journey and hope this story brings a smile to your face… …..</p><p>For those meeting me for the first time, I’m <strong>Coy Emerald,</strong> a penetration tester passionate about writing on <strong>cybersecurity</strong> , <strong>ethical hacking</strong> and sharing some of my amazing <strong>experiences</strong> as a security researcher i.e <strong>bug bounty hunter</strong>.</p><p>I’d like to clarify that I didn’t reject the bounty amount offered by <strong>AT&amp;T</strong> solely because it was too low. As I’ve previously mentioned even to them, I’m willing to justify why I believe I deserve a more substantial bounty for these reports, rather than the minimal amount offered.</p><p>While writing this story, I received a bounty award notification from another bug bounty platform where I had reported a vulnerability.</p><p>Even though the rewarded amount was<strong> low</strong>, I’m content to accept it without further discussion, as I believe it accurately reflects the report’s severity. I’m satisfied with the company’s decision.</p><p>I mention this to illustrate that my concerns aren’t solely about the bounty amount; rather, it’s about feeling <strong>undervalued</strong> and seeking fair recognition for my efforts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*uMsdQ2R5ItaUXLqBcFPVfQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*tVThKzzUyrLwug4bg9oHtQ.jpeg" /></figure><p>As a <strong>responsible hacker</strong>, I operate within established guidelines and respect the rules. In line with this ethos, I <strong>ensured that both ATT and HackerOne received a copy of this</strong> <strong>story</strong> for review on <strong>August 13, 2024</strong>, before sharing it publicly. This approach allows for <strong>transparency</strong>, <strong>accuracy</strong>, and demonstrates my commitment to <strong>collaboration</strong> and <strong>ethical disclosure</strong>.</p><p>So, I forwarded this story to them on <strong>August 13, 2024,</strong> and received a response just hours later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*ZzJMS289ahMhKmXXXTCYQg.jpeg" /></figure><p>On this same <strong>August 13 2024</strong></p><p>I received confirmation from <strong>HackerOne</strong> that <strong>AT&amp;T</strong> had received my story- this same story.</p><p>In their response, they noted: &#39;There are several factual inaccuracies in this article. We would like to discuss this with you further.&#39;</p><p>This indicates that they have just <strong>found a bug</strong> in my story 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*jVwXCbcJX3EUQxYo1_-mFw.jpeg" /></figure><p>Well, I agreed to delay the publication of this story until today, <strong>August 14, 2024.</strong> Meanwhile, I’ve requested a working proof of concept to substantiate their claimed inaccuracies (which can be considered as their own discovered vulnerability 😂 in my story)</p><p>And If they fail to provide it in timely manner, I’ll consider their comments on the shared story with them as <strong>out of scope</strong> or merely <strong>informative</strong>. 😂</p><p>While waiting for their further discussion and response regarding the <strong>alleged inaccuracies</strong> in this story, I continue to find vulnerabilities in the active platform (not websites) we’re using to communicate.</p><p>As those who know me well can attest, I take great pleasure in identifying web application vulnerabilities. And, amazingly, I found a small bug in their previous response as well 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*8GPlNEyPuzCIKUj8h2zbCg.jpeg" /></figure><p>A few hours later,I received a response <strong>clarifying the new bug I had pointed out</strong>, and I’m <strong>satisfied with their explanation.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*55Tog2nXnrP0touDkZkSNA.jpeg" /></figure><p><strong>However</strong>, I’m <strong>still awaiting their feedback on the alleged inaccuracies</strong> in this story. I’m confident that I’ve provided a truthful account of my experience with both <strong>AT&amp;T &amp; Hackerone</strong> , shared in good faith and in accordance with responsible disclosure principles.</p><p>At around <strong>7:55 PM on Tuesday, August 13, 2024 WAT,</strong> I received another unexpected message through <strong>HackerOne</strong> from another <strong>AT&amp;T staff</strong> while I was still awaiting feedback from AT&amp;T regarding the <strong>alleged inaccuracies in</strong> this story, which they had mentioned in their previous responses.</p><p>The message informed me that the reported issues <strong>had been fixed</strong> — Ẹ sọ́ wi pẹ Allahu Akbar 😂</p><p>Unexpectedly, I also read through this recent message from them that they are &quot;<strong>concerned about several inaccuracies in your blog</strong>, i.e., this story.&quot;</p><p>First, when I was also concerned about several inaccuracies in the security of their server and overall organization, in accordance with the global responsible disclosure policy, I continued to report to them <strong>with proof of concepts</strong>, which they had also encouraged me to do. 😂</p><p><strong>For several hours now, I’ve been asking myself: why haven’t they pointed out any inaccuracies in this personal story of my encounter with them?</strong></p><p>This response annoyed me to the point where I even reached out to a US government agency via <strong>Twitter</strong> to ask for an update on their investigation into the recent AT&amp;T breach, as they had claimed to be conducting an investigation into the matter.</p><p><strong>And to inform them prior to the publication of this story, as I plan to share my personal experiences as an ethical hacker with the public.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*0qMVXX0nzIWD3RE-XvxtyA.jpeg" /></figure><p><strong>Part of their response also stated:</strong></p><p>“Most importantly, the issue you reported appears to involve <strong>one customer with multiple entries</strong> on their <strong><em>kinikan</em></strong> application. The links you found were <strong>intentionally configured</strong> by the <strong>customer to be publicly accessible.</strong> The <em>affected files</em> are <strong>no longer available.” 😂</strong></p><p>I also found this part of their response amusing, because initially they claimed the exposed data was USERS’ faults ,but now only affected one user, which I believe was a lie. If that were true, they might not have even bothered to fix the issue, and I certainly wouldn’t have continued to press them to resolve it to prevent another <strong>breach</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*ugHHnhrS-Jg2CNubMH-HaA.jpeg" /></figure><p>On <strong>Tuesday, August 13, 2024</strong>,</p><p>I <strong>confirmed that the issue had been fixed and felt a sense of fulfillment</strong>. I then moved on without accepting their offered bounty 😎</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*_CxhR5WBMdOMlJOc77j7jw.jpeg" /></figure><p>While I was still waiting for their response, I discovered another vulnerability on the same domain where they had recently fixed an issue. I don’t know what you would do in my shoes, but I decided to report it to them anyway 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*NZ5p_ZSnWkodlBFD6nqjDg.jpeg" /></figure><p><strong>Note</strong>: I didn’t bother waiting for their comments on the reported issue, as it’s their sole decision to determine how it has affected their organization. I had already made <strong>my decision</strong> and requested permanent account deletion by contacting HackerOne</p><p>If <strong>HackerOne or AT&amp;T</strong> wish to <strong>correct any inaccuracies</strong> or share their side of the story, they’re welcome to do so on their own platforms, I’d be interested interested in reading it!</p><p>Honestly, <strong>bug bounty hunting is fascinating and full of amazing experiences</strong>. However, when an ethical hacker feels that a company or platform lacks transparency, I believe the best course of action is to <strong>walk away</strong>. And if an ethical hacker feels been played, I don’t know about others, but personally, I will play back if I can ✊</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*aAR8azX1FbrFlLhy-CG-dg.jpeg" /></figure><p>Back to <strong>July 25, 2024, 12:06 PM UTC</strong></p><p>Ever since I began to feel that this platform lacks transparency,</p><p>I have already started seeing them as a joke 🤣 though I continue to report whatever I can find to them.</p><p>I now <strong>withhold reproduction steps</strong> until I receive confirmation from the <strong>triage team.</strong> Please refer to the screenshots below for an example of my <strong>playful reporting</strong> format. 😂</p><p>- <strong>Details/Description of the vulnerability</strong><br>- <strong>Confirmation of the status of similar report</strong> <br>- <strong>Proof of Concept (POC)</strong></p><p>Please note that I have intentionally <strong>excluded the reproduction steps</strong> from this report</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*AnaMO_ZiointWkdU04REFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Ddc_taUXBqeWU2zOvLjIIg.jpeg" /></figure><p>I later sent the reproduction steps, although the vulnerability submission was marked as &quot;informative&quot;. This is correct, as I couldn’t exploit it. However, I’m glad that he experienced the same trouble that researchers face when disclosing vulnerabilities to them. Ironically, some of their team members can be just as rude as the hackers they deal with 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*j1hbYnQgh0myJUfQc70d5w.jpeg" /></figure><p>it’s just confusing when <strong>AT&amp;T staff</strong> and the <strong>HackerOne triage team </strong>cannot determine if an issue is valid or not. It’s even more concerning how a giant telecommunications company like them will have a policy as this <strong>&quot;AT&amp;T reserves the right of non-remediation in its sole discretion</strong>”</p><p>Meaning that they may <strong>choose not to fix a reported issue, even if it poses a risk to their customers or systems.</strong></p><p>Well, this is their decision though.</p><p>While writing these stories, I received submissions from other ethical hackers, including my <strong>trainees</strong>, around the world who have had similar negative experiences with the <strong>HackerOne platform</strong> and <strong>AT&amp;T’s Disclosure Program</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*21R-KHO2tu6_ALsESh_b3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*xq81TzVgA2seqPYf7cHSbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*Eo-NcaI7SjD06Ebp_Qv_0g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/718/1*-C6tDTKmREXOOABNos8dcg.jpeg" /></figure><p>Following my recent experience with <strong>AT&amp;T</strong> and this latest incident, I am compelled to question the credibility of both the <strong>HackerOne</strong> platform and <strong>AT&amp;T’s security research</strong> program.</p><p>Well, I thank <strong>AT&amp;T</strong> for the first bounty offered earlier and I also <strong>appreciate the opportunity to have worked on their platform , </strong>I gained valuable experience through their platform, and I’m grateful for that.</p><p>As of <strong>August 14, 2024</strong>, I have decided to <strong>discontinue</strong> my security research activities on the <strong>HackerOne platform</strong>, effective immediately.</p><p>Since most of my research was already being conducted outside of their platform, I have now decided to leave the HackerOne portal completely .</p><p><strong>Note</strong>: Everyone has different opinions and perspectives on any bug bounty platform. <strong>For me, HackerOne has never been a perfect option.</strong> Ayọ́juran lo gbé mi dé bẹ 😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Ell-9ZZDWoSBTCpyjHXrpQ.jpeg" /></figure><p>And <strong>If you think I was wrong to firstly rejected their reward, wait and continue researching – you’ll eventually understand my perspective</strong>! Special thanks to <strong>a friend </strong>for his support in sharing this story.</p><p>To my <strong>other friends and trainees in the infosec community</strong>: I’m sending you all best wishes for continued growth, learning, and success in your hacking pursuits.</p><p>May your skills remain sharp, and your passion for security remain strong!<strong> -</strong> keep pushing boundaries, and always remember to do so responsibly!</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf"><strong>https://selar.co/1848uf</strong></a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ca2e31c302" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to steal the traffic from other people’s websites to your own website.]]></title>
            <link>https://medium.com/@coyemerald/how-to-steal-the-traffic-from-other-peoples-websites-to-your-own-website-75dd2063c3a6?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/75dd2063c3a6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defacement]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Mon, 03 Apr 2023 01:05:35 GMT</pubDate>
            <atom:updated>2025-01-04T07:58:56.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, I would like to discuss how hackers redirect another person’s website to their own (preferred) Website.</p><p>This might look like an <strong>Offensive </strong>tutorial- but it is <strong>NOT</strong>! Because, even as an <strong>ethicalhacker</strong> , knowing the offensive part of hacking (and not practicing it) is what will build you up to become an expert in this field of <strong>cybersecurity</strong></p><p>However, and by continuing reading this, you agree that I <a href="https://linkedin.com/in/coyemerald"><strong>Coy Emerald</strong></a> do/will not bear any responsibility for any wrong use of this published information, as I do not bear any responsibility for the wrong use of all my older posts — <strong>Temi tomi leru</strong>, please don’t add to it!</p><p>There was once upon a time, a long time ago, that I also did the defacing of a vulnerable website (s) I think many (good) hackers of today have also passed through this phase, but then my face has not really been showing and just like it is now, even my shoe wasn’t shinning —lol, but <strong>Alhamdulilahi</strong> for where I am today &amp; <strong>Auzubillahi</strong> from all the temptations of having the <strong>blackhat</strong> thoughts.</p><p>With my experience now, I am not really proud of some of my past activities, especially the #defacement part; it was too childish even though I’ve done more of this with the “permission” of the domain administrator- some dev only accepted it as<strong> POC</strong> (see the attached photo ) Well, Yoruba had said, “<strong>iriri lagba”</strong> — this can be translates as “<strong>experience is the best teacher”.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/899/1*dVWCQGBFXsCVdxu-GWq8Kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*gdbQxKjE5zdd_aw4XYyRpA.jpeg" /></figure><p>As always, I do not encourage any unethical part of <strong>hacking</strong> and Please, also know that defacement of any part of a website can easily affect a website by damaging its reputation and it can also lead to a business breakdown — so <strong>do not deface the web</strong>!</p><p>I won’t be surprised if you don’t really know me, then, because I was actually a <strong>“ghost hacker</strong>” until I removed my mask — not a threat, but those who have long known me, know that I am not to toy with.</p><p>As an <strong>ethicalhackingtrainer</strong> and because I’ve also been asked by someone who has clicked on a website (A) and strangely finds himself on another website (B) that has nothing to do with where he has clicked on — as the browser has redirected the visited website to somewhere else that he has not intended to go and to another domain that doesn’t’ affiliated to the origin</p><p>Therefore, I think I should publicly answer this as it has been one of the unethical but helpful things that people with low traffic on their website/ blog often do, to get or steal the traffic from other people’s websites, which is vulnerable to #hacking</p><p><strong>So, how does this illegal redirection happen?</strong></p><p>All they have to do to redirect another person’s website to their own preferred website is by accessing the website through the uploaded <strong>“webshell”</strong> in the vulnerable domain.</p><p>And by replacing the original code of the <strong>“index.php” , “index.html” </strong>or even the<strong> “home.html”</strong> with a simple redirection code as below</p><p><strong>&lt;meta http-equiv=”refresh” content=”3;url=http://www.coyemerald.com/&quot; /&gt;</strong></p><p>By putting the above code or another redirection code in the “index file” inside the public_html or in any of the pages, such website or the modified page will be redirected to another website as I have used my website “coyemerald.com” in the above code and the unknown visitor (s) of the affected website may not even understand what’s going on.</p><p><strong>Take Away For The Dev:</strong></p><p>(1) Always Restrict Having Direct Access To Your Website Directory- Implement <strong>403</strong> rule</p><p>(2) Create a blank file, name it .htaccess and paste the following code in there:</p><p><strong>&lt;Files *.php&gt;</strong></p><p><strong>deny from all</strong></p><p><strong>&lt;/Files&gt;</strong></p><p>Put this file to your site directory. For example, <a href="https://coyemerald.com/wp-content/uploads/.htaccess">https://coyemerald.com/wp-content/uploads/.htaccess</a> folder</p><p>To check for any uploaded “<strong>.php file”</strong>, or specify any other file type that you would like to deny illegal access to</p><p>(3) Always use a trusted and reliable <strong>penetrationtester</strong> to check your code for you- the only use of succuri can never secure your code and I can best offer you this service!</p><p>My Contact email address <a href="/service/mailto:security@coyemerald.com"><strong>security@coyemerald.com</strong></a></p><p><strong>Tips for the hunters (hackers):</strong> always check for <strong>.php, .html</strong> or any other <strong>invalid file</strong> type in an images directory. I’ve many times found backdoor or other sensitive/config information by checking for this through an unprotected web directory.</p><p>Note: If you are interested in learning more about the techniques used to add a backdoor (web shell) into a website, or if you require my service of <strong>fixing your hacked website</strong> or for other cyber security services such as web application <strong>penetrationtesting </strong>service</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf"><strong>https://selar.co/1848uf</strong></a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75dd2063c3a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Something they may not tell you as a #cybersecurity researcher ]]></title>
            <link>https://medium.com/@coyemerald/something-they-may-not-tell-you-as-a-cybersecurity-researcher-50764d09a24c?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/50764d09a24c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[coyemerald]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 09:25:33 GMT</pubDate>
            <atom:updated>2025-01-04T07:58:34.133Z</atom:updated>
            <content:encoded><![CDATA[<p>Something they may not tell you as a #cybersecurity researcher 😉</p><p>Security vulnerabilities are discovered all the time and there are good people who are responsibly reporting them directly to the organization before the malicious actors find out</p><p>Reporting of a vulnerability provides valuable information for the vendors (of the affected products) so that they can be used to improve the security of their systems. It is a perfectly good idea to always encourage researchers to disclose a confirmed vulnerability. But the way some companies often treat some researchers like a thrash is alarming. For those who may not understand this, the way the public is being told about vulnerabilities is called &quot;disclosure&quot; or &quot;vulnerability disclosure&quot;. However, it is a controversial subject and it is constantly being debated.</p><p>When a researcher discovers the vulnerability, this is when the Window Of Vulnerability (WoV) time-frame begins and at this point, the vulnerability is also known as a Zero Day, since it might only be known to the discoverer.</p><p>But if a researcher can contact the vendor privately and let them know that they have a security problem and supply the details.</p><p>Why discourage him ? Why threaten him ? The fact is, malicious hackers would have chosen not to disclose vulnerabilities to both the vendor and the public because they want to use them to do damage.</p><p>At this point of my life, If I ever find a bug in any vendor&#39;s products again and if it&#39;s critical - because I&#39;m a responsible hacker, I&#39;ll responsibly report this to the appropriate team and I will wait for a maximum of 30days (and if there&#39;s no response) I&#39;ll optin for the forcedisclosure 😂 however, you may inform your police 🤓 k&#39;olọ̀pa wa kò everybody 😂</p><p>Sadly, some vendors will receive a vulnerability disclosure from researchers and instead of appreciating his good decision (intent) they&#39;ll choose to threaten him.</p><p>For example, six months ago, I discovered a vulnerability on #ChipperCash as always. I contacted them and after they had received the full reports of my discovery, it was acknowledged and I was asked to wait.</p><p>A few weeks ago, I was contacted again, and they asked if I am still following up on the case (via DM) NOW. They&#39;re snubbing and ignoring me- Orí Yín Tí Gbà Lẹ</p><p>Some of you may be wondering why a researcher would want to release the full details of a security hole or vulnerability to the public at all?</p><p>Researchers are human too 😂 Security researchers make their living through consulting and selling security products and services. And doing security research costs time and resources, so researchers need to be compensated for this investment and by announcing to the world that they have discovered an important vulnerability, this may help the public to be aware of the threats in order to take proper action and also to market their products and services.</p><p>Releasing full technical details of a vulnerability by a researcher illustrates the great work that they’re capable of and helps them cover their expenses, make a living and helps fund future research.</p><p>Important to Note: There are lots of critical vulnerabilities that can be accidentally found even without running any tools and if a researcher can be good to the vendor , how on earth would a vendor be treating researchers as a thrash!</p><p>Till now, I still care to know why ChipperCash has chosen to snub Me after we reached an agreement via their verified Twitter page!</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf">https://selar.co/1848uf</a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50764d09a24c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The website is the connection point for all of us, as it has been a host even for LinkedIn.]]></title>
            <link>https://medium.com/@coyemerald/the-website-is-the-connection-point-for-all-of-us-as-it-has-been-a-host-even-for-linkedin-41b413e80395?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/41b413e80395</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[website]]></category>
            <category><![CDATA[penetration-test]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Mon, 23 Jan 2023 06:46:42 GMT</pubDate>
            <atom:updated>2025-01-04T08:01:48.051Z</atom:updated>
            <content:encoded><![CDATA[<p>The website is the connection point for all of us, as it has been a host even for LinkedIn.</p><p>Websites are also a major tool for a malicious user and the victims, and with little coding knowledge, someone can easily create a #fraudulent website that will appear even more legitimate.</p><p>Some of these fake websites can also display almost like the original, and it can be very convincing and confusing!</p><p>For less technical people, it’s a bit difficult to identify a real website and a website developed for a fraudulent purpose.</p><p>As your trusted cyber security friend, I would like to mention below some of the signs to indicate that you are dealing with fraudulent websites.</p><p>(1) <strong>Abused SSL Certificate</strong> : That a website shows a padlocked icon doesn’t indicate that such website is not a fake/malicious website – know this very well, even a fake website address may have its address beginning with “https”</p><p>So, if you are referring to a website or giving a link to login, don’t just believe that it is a safe website simply by seeing the “Connection secured” message.</p><p>Because even an https website can be vulnerable to hacking, and a malicious person can also host or build his fake link (usually a fake bank login link) on this affected domain so as to convince the victims that the website is genuine.</p><p>Therefore, understand that the “https” sign is not a guarantee that you’re on a safe website-“https” can also be purchased even for a fraudulent website – so be more vigilant!</p><p>(2) <strong>Spelling Error</strong>: If the website’s name also has any noticeable spelling mistakes and errors, it is mostly an indicator that the website you are visiting is Fake.</p><p>While on some websites, if you see bad grammar, wrong phrasing or spelling mistakes in them, it can mean a simple bug – as a Bug Bounty Hunter, I’ve many times reported this and received a “ThankYou” from the domain owner after fixing it – but if there’s a spelling error in to url name, this actually mean that you should proceed on that site with caution and you should pay much attention</p><p>(3) <strong>Hosting/Domain Registration Period</strong> – Most of the fake websites were created recently and the availability of the website is very short because, most of these fake websites get suspended quickly after there are reports (from the victims) or if they&#39;ve been marked as a deceptive website by researchers.</p><p>So you should always verify the creation period or the time that the website has been in existence - there are many online investigation tools/ websites that you can also use,</p><p>But for $2 , I will provide adequate and useful things you need to know about any website.</p><p>However, also be informed that the long registration period of a website does not always indicate the legitimacy of a website, but in most cases, it counts!</p><p><strong>(4) Googling-</strong> Google will help you to do a quick review and show the relevant comments and information about the website you are referring to,</p><p>Just like if you do a simple Google search for my name “<strong>Coy</strong> <strong>Emerald</strong>”, you’ll be shown with a lot of information that will tell you more about me as a &quot;<strong>Cyber Security Specialist</strong>&quot;.</p><p>As a search engine, Google is a useful tool and the easiest method to uncover fraudulent websites. In fact, the website you just want to visit might have been listed/flagged somewhere else as a scam.</p><p>(5) <strong>Invalid Contact Phone Number/Support Email Address</strong>- Mostly, the phone number that appears on a fraudulent website is not a valid number. If you attempt to call or text this number, it won’t be available and if you send a message to the email address, it will also bounce back.</p><p>So, if there&#39;s a claim on a company&#39;s website that they have an office in a foreign country or elsewhere, do check their contact information and confirm the availability of the number you see on the contact page.</p><p>However,</p><p>If you are unsure of the website you are referring to, or you would like to know if a website you are trying to deal with is authentic ,safe or not?</p><p>​And for your peace of mind, please, always contact me either through my information below for a quick and perfect review.</p><p>I am always available online 24 hours, 7 days.</p><p>https://www.linkedin.com/company/o-range-cyber-security-training-services-ltd/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*3wkrMBOhuRJmbXm0IqllZg.png" /></figure><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf">https://selar.co/1848uf</a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41b413e80395" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guidelines For Reporting Vulnerabilities (Bugs)]]></title>
            <link>https://medium.com/@coyemerald/guidelines-for-reporting-vulnerabilities-bugs-d4c0f087a9ad?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4c0f087a9ad</guid>
            <category><![CDATA[bug-bounty-tips]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[tricks]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Tue, 10 Jan 2023 05:35:23 GMT</pubDate>
            <atom:updated>2025-01-04T08:01:10.701Z</atom:updated>
            <content:encoded><![CDATA[<p>Dear Ethical Hackers! especially beginners at bug bounty hunting,</p><p>It is really hard to fix a vulnerability if the person looking into the submitted bug reports cannot reproduce it.</p><p>Understand these before submitting bug information,</p><p>1. As a beginner and for your peace of mind, <br>Always seek permission before testing a website that did not have a Bug Bounty Program or VDP. However, just because a website doesn’t have a responsible disclosure program shouldn’t be a restriction for you to report a CRITICAL vulnerability and it will also not invalidate your valid bug report!</p><p>As a Coinme first bounty recipient, when I discovered what I discovered on their website <a href="https://coinme.com/">https://coinme.com</a>, I just reported it without even checking if they have a BB program or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/506/1*jbDtKsXBDq-65d0eG6m2XQ.jpeg" /></figure><p>Take Note: Ethical hackers do many things with rules &amp; not against them- but, the fact is, there are many bugs, even critical vulnerabilities that can be accidentally found &amp; without even the run/use of any scanning program.</p><p>2. Try as much as you can to avoid users’ privacy violations i.e. do not exploit any findings/discoveries that require accessing the user’s account</p><p>3. Keep the information about any vulnerabilities you’ve discovered confidential between yourself, and unless you are working as a team, don’t share your findings with any third party.</p><p>4. Act in good faith, giving the company/website a reasonable amount of time to reply to your reports and resolve the vulnerability before publicly disclosing it, is an important decision. It doesn’t matter how long it takes you to get in touch with the security team.</p><p>Remember this, it has taken me several months or even a year to have gotten in touch with some web security team &amp; till the time that I’m making this write-up, <strong>Tue, Jan 10, 2023</strong>, I still have many 2020,2021 reports that I’ve submitted &amp; still has 0 responses, yet, they’re not false reports. my point is, Being an <strong>Ethical-Hacker</strong> also requires patience!</p><p>5. Make your bug report to be very clear and understandable, so the person receiving the report will be able to reproduce or verify it. Otherwise, you can simply make a video demonstration instead!</p><p>Know this very well,<br>It is hard to fix any issues you might have discovered if you did not report them accurately.<br>&amp; unlike any other field, complex English is needless, your fluent English is also a joke if your POC is not reproducible!</p><p>6. If any organization asks you to stop contacting or reporting bugs to them, I advise you to <strong>STOP</strong> &amp; just do as they have said! <br>In most cases, you’ll always encounter this if the administrators of the website you are reporting to are ignorant of who the “ethical hacker” is. And sometimes it’s their arrogance and ignorance that will make them respond to you wrongly — dear fellow ethical-hackers, especially beginners, don’t be discouraged by these unpleasant reactions.</p><p>I’ve encountered several of these too. The fact is, it’s really hard to get people interested in what has not affected them i.e. unexploited bug<br>I’m encouraging you to look into <strong>Hackerone</strong>, <strong>Bugcrowd,</strong> and even <strong>Intigriti’s</strong> program<br>Thousands of domains are out there that will surely appreciate and reward your good work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/398/1*6lxc8TSk92NoSFNtci7Vuw.jpeg" /></figure><p>Though it takes a crowd and even time to earn a bounty from the above-mentioned platforms, the only unpleasant response you’d get there is “Sorry, it’s a Duplicate “. Or that they need more information- N/A” but not like one of the funniest but dumbest responses that I’ve received from one developer/administrator.<br>Well, 5 years ago, I was actually a little hacker when I got this mail, LOL</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*b3pqFhJ0zUl6bcJWFNzSEw.jpeg" /></figure><p>Addition: For those working outside H1, BC, or Intigriti, here are the samples of the brief message that you can also use to submit a “bug report” even through the “<strong>contact us</strong>” page of the website</p><p><strong>Sample I</strong></p><p>Hello Administrator/Developer, <br>Just yesterday ( insert the day) I came across your website and I discovered security bugs on the website. Even though you did a great job with the design and content, you can’t ignore the security part of it so as to avoid the website breaking and protecting vital information on the server.<br>Therefore,<br>I am writing to report the discovered vulnerability in your domain</p><p>Affected Website: Affected Website<br>Vulnerability Path:(mention where you’ve found the bug in the website)</p><p>I am contacting you about this website vulnerability which allows attackers (intruders) to tamper with site files and modify the website contents. I have a more valid proof of what I am saying.<br>Although this website (affected website) still works correctly, if the problem or the bug is known &amp; revealed to a malicious hacker, the whole website can be compromised. I am happy to explain the bugs to you upon your request and after you reply to this message.<br>Be assured, I am a Cyber Security Professional –Ethical Hacker, so nothing to be afraid of, as I am just contacting you in order to inform you and fix the discovered bugs <br>Regards<br>(Your Name)<strong><br>Cyber Security Expert</strong></p><p><strong>Sample II</strong><br>Technical Analysis &amp; Bug Report<br>Researcher: (Your name)<br>Domain: <a href="https://coyemerald.com/">https://coyemerald.com</a> <br>Bug Type: Developer Mistake <br>Vulnerable Path: <a href="https://coyemerald.com/ignorantarroganttechsupportteam/">https://coyemerald.com/ignorantarroganttechsupportteam/</a></p><p>POC:<br>Briefly discuss the reproduction steps. <br>Alternatively, you can add video instead by making screen recordings.<br>Regards,<br>(Your Name)</p><p>Note: Always make your report simple, very clear, and reproducible and, if you’re contacting any security team through email support, you can make use of one of these unique subjects such as</p><p><strong>“I found a bug!”, “Something’s not right”, I think I should let you know”, “Vulnerability Disclosure”</strong></p><p>I mentioned all these to give helpful insights and to also discuss a few of my 10-year experience of being a Bug Bounty Hunter briefly.</p><p>And in the next 10 days, I’ll be 27yrs old 😍</p><p>I’m ending this note by wishing myself a very <strong>happy birthday in advance</strong>!</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Hunting Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf">https://selar.co/1848uf</a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4c0f087a9ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I found a critical P1 bug in one of Google’s products- with google]]></title>
            <link>https://medium.com/@coyemerald/how-i-found-a-critical-p1-bug-in-one-of-googles-products-with-google-1c11352eba6f?source=rss-297960842acd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c11352eba6f</guid>
            <dc:creator><![CDATA[Coy Emerald]]></dc:creator>
            <pubDate>Sat, 10 Sep 2022 16:24:55 GMT</pubDate>
            <atom:updated>2025-01-04T07:28:08.601Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello hackers,</p><p>My name is <strong>Coy Emerald </strong>&amp; I’m from somewhere in the western part of Africa, <strong>Nigeria</strong>.</p><p>On <strong>Aug 21, 2022,</strong> I was at home working on my laptop and updating some information on my website<strong> </strong><a href="https://coyemerald.com/"><strong>https://coyemerald.com</strong></a> and I decided to check for something on Google.</p><p>I clicked on one of the search results, and this took me to one of the google subdomains *****.<strong>withgoogle.com</strong></p><p>While on this page, I found that <strong>Django Debug Mode is Enabled</strong> &amp; I felt excited😍 because I’m certain that, <strong>I’ve found a bug</strong>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*ID2HUo8iVWVelclNorq5Iw.jpeg" /></figure><p>After seeing this, I opened my “<strong>Burp Suite</strong>” to escalate this discovery into real <strong>vulnerability</strong></p><p>All I did was I revisited one of these paths on “<strong>burp</strong>” and I intercepted the request by changing the “<strong>GET</strong>” request to “<strong>POST</strong>” and boom! this leads to the exposure of sensitive information such as the detailed traceback, including a lot of metadata about Google&#39;s environment, and some currently defined Django settings.py files and other script files</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZrfTM04mNjA_vXx1W5MYHg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i-GdukYGqtrtBhUnZJ5w8Q.jpeg" /></figure><p>After I saw these, I felt more excited and I proceeded to contact Google and I reported this to them,</p><p>On the next day, <strong>Aug </strong>22, <strong>2022, </strong>I received a message from <strong>Google Security Team </strong>that my bug submission was accepted and had been logged</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6Lwd_rPyyN6oe6aEvkv13w.png" /></figure><p>Again, I am more excited because I couldn’t believe I got my first <strong>P1 CRITICAL vulnerability</strong> in less than 5 MINUTES on Google products.</p><p>You know that joy that makes you want to scream “<strong>O Por</strong> ” 😂 any Yoruba people reading these would agree with me that “<strong>O Por Pa</strong>” 😂</p><p>Surprisingly, Google only rewarded my discovery by mentioning my name on their Honorable Mentions page but It feels really good that I found something (vulnerability) that was so important to Google</p><p><a href="https://bughunters.google.com/profile/0bd3c7c9-cb57-4b87-a46c-3edbf6187eaf">https://bughunters.google.com/profile/0bd3c7c9-cb57-4b87-a46c-3edbf6187eaf</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96CN5mFZSqcU0Pnp81I_2A.jpeg" /></figure><p>That was my short story about Google &amp; I hope you enjoyed it</p><h3>Get in Touch</h3><p>For questions, collaborations, or to learn more about <strong>bug bounty hunting</strong>, connect with me on:</p><ul><li><a href="https://linkedin.com/in/coyemerald">LinkedIn</a>: <a href="https://linkedin.com/in/coyemerald"><strong>https://linkedin.com/in/coyemerald</strong></a></li><li><a href="https://twitter.com/@coyemerald1">Twitter:</a> <a href="https://twitter.com/@coyemerald1"><strong>https://twitter.com/@coyemerald1</strong></a></li><li><a href="https://facebook.com/coyemerald1">Facebook:</a> <a href="https://facebook.com/coyemerald1"><strong>https://facebook.com/coyemerald1</strong></a></li></ul><h3>Unlock Your Bug Bounty Potential</h3><p><a href="https://selar.co/1848uf">Click to get The Ultimate Bug Bounty Hunting Course:</a> <a href="https://selar.co/1848uf">https://selar.co/1848uf</a></p><h3>Thanks for Reading!</h3><p>Coy Emerald</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c11352eba6f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>