VirusTotal
3 / 92 engine detections
Open reportcovabeans.co.kr is a Gmail impersonation page detected by PhishDestroy on 2026-09-27. Risk: critical (81/100). Registrar: Megazone(http://HOSTIN…. Status: Last known active. Hosting: IQWeb FZ-LLC. PhishDestroy sent 1 abuse report. VirusTotal: 3/92 engines flag it. Do not enter credentials or connect a wallet.
“코바빈스 | 커피는 이제 자산입니다 - 프리미엄 원두 투자 플랫폼”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@iqweb.io.
The latest stored availability evidence still shows the domain reachable; 24 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
3 / 92 engine detections
Open reportScan report
Open report4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
covabeans.co.kr is an impersonation phishing page dressed up as "코바빈스" (Covabeans), a Korean-language platform that claims coffee beans are now an investable asset. It targets Korean-speaking people looking for alternative investments with steady returns. PhishDestroy first flagged it on 2026-09-27. When last checked on 2026-10-19, the site was still online and serving its content.
The page title translates to "Coffee is now an asset – premium coffee bean investment platform." It sells green or premium beans as a commodity with promised yields. Schemes like this usually invite visitors to register, hand over identity and bank details, and deposit money into a dashboard that shows growing profits. When victims try to cash out, they are typically asked for "fees," "taxes" or extra deposits, and the money never comes back. Victims stand to lose every deposit plus the personal data they submitted. The title presents a standalone investment brand, while we classify the site as impersonation.
Independent detection is still thin. On 2026-10-10, 3 of 92 VirusTotal engines flagged the domain: Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. PhishDestroy is the only blocklist carrying it so far, so most browsers and filters will not warn visitors. Four AlienVault OTX threat pulses reference it, which shows other researchers are tracking the same activity.
The domain was registered on 2026-08-26 through Korean registrar Megazone, roughly a month before we detected it. That short gap fits a site built for a single campaign. Despite the .co.kr name and Korean branding, it is hosted outside Korea on the IQWeb FZ-LLC network at 186.2.175.145, with the server located in Belize. It uses a free Let's Encrypt certificate, so the padlock in the browser proves nothing about whether the platform is legitimate.
Do not deposit money, and do not pay any "withdrawal fee" or "tax" to unlock a balance. Those payments only deepen the loss. If you already sent funds, contact your bank or card issuer right away to try to stop or reverse the transfers, and file a report with the police. If you submitted your ID, phone number or bank details, watch for follow-up fraud and "recovery" offers, and change any password you reused on the site. Defenders should block the domain and its hosting IP, and warn Korean-speaking users about coffee and commodity investment pitches.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0e446-bd78-731d-8d8e-265cb0546c9b |
|---|---|
| Final url | https://covabeans.co.kr/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://covabeans.co.kr/",
"from": "http://covabeans.co.kr/",
"status": 307
},
{
"to": "http://covabeans.co.kr/",
"from": "https://covabeans.co.kr/",
"status": 307
},
{
"to": "https://covabeans.co.kr/",
"from": "http://covabeans.co.kr/",
"status": 301
}
] |
| Ip | 186.2.175.145 |
| Ptr | ddos-guard.net |
| Contacted domains | [
"cdn.jsdelivr.net"
] |
| Contacted IP addresses | [
"151.101.193.229",
"186.2.175.145"
] |
| Asns | [
"54113",
"59692"
] |
| Countries | [
"US",
"AE"
] |
| Document hash | c39c48c80baebc3410895707660372beb72685a0c44c3fa4cb4d17aca549d3fb |
| Script hashes | [
"9b422073246a4c528a2dc585b320ccf164f7405ac6ca10cad104aa8da7827b1a",
"6f8c4911131bbeafaafafec7bc781e4beb7eda6de02d9b08c3293206be981854",
"e9f765c5c0f5e2a28894227989ec3e079c4c1db7a40ee936f9dfe662db4f2d0c",
"be9185d18685b530bb2ed18b822362c5e27cb199e6cb94eeb85b4261600d9719",
"7bdff7987f8d8c586d62113954ef4240f7e2d8211dbca978916e4a614df9bcdb",
"a3abc941e792f71aa3e9bd147a4a7ce65006d54bfa417a8604adf05dd9cee308",
"63d8f373b6dad78cbec670a958606582535abd6aa149ac824eac80a821f75898",
"bfc63e2276a3200ee8eac9e1c02e276f2a32461225feb0fea84560e6fe48c313",
"e9786b1305894e4119bb9811a816dac9cf576755596dd989ee15b455749fc35e",
"a6248517cd3ee53a8186b51c59e1e764e3dc0c512f4acbd50e818f9884663e21"
] |
| Globals | [
"requestResize",
"__next_f",
"TURBOPACK",
"next",
"__webpack_hash__",
"_N_E_STYLE_LOAD"
] |
| Cookies | [
"__ddg9_",
"__ddg1_",
"__ddg10_",
"__ddg8_"
] |
| Tls | {
"san": [
"covabeans.co.kr"
],
"cipher": "AES_128_GCM",
"issuer": "YR2",
"subject": "covabeans.co.kr",
"protocol": "TLS 1.3",
"valid_to": "2026-11-24T07:27:45Z",
"valid_from": "2026-08-26T07:27:46Z"
} |
| Domain age days | 32 |
| Apex age days | 32 |
| Tls age days | 32 |
| Tls valid days | 89 |
| Requests | 33 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 88,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "ddos-guard",
"content-type": "text/html; charset=utf-8",
"x-powered-by": "Next.js",
"content-security-policy": "upgrade-insecure-requests;",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin-when-cross-origin"
} |
Observed: · Retrieved:
| Uuid | 6a8cb620-4aa0-4ef6-a613-1460c18bf627 |
|---|---|
| Final url | https://covabeans.co.kr/ |
| Status | 200 |
| History | [
{
"url": "https://covabeans.co.kr/",
"status": 200
}
] |
| DOM structure hash | b4736b1f4cbe10922d44bf08e6183511532d288892bafeaa057bcf157aa8cfc6 |
| Document hash | c39c48c80baebc3410895707660372beb72685a0c44c3fa4cb4d17aca549d3fb |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "covabeans.co.kr",
"type": "A",
"value": "186.2.175.145"
}
] |
| Dnssec valid | false |
| Ip | 186.2.175.145 |
| Registration record | {
"registrar": "Megazone(http://HOSTING.KR)",
"created": "2026-08-26T00:00:00Z",
"updated": "2026-08-26T00:00:00Z",
"expires": "2027-08-26T00:00:00Z",
"nameservers": [
"ns1.ddos-guard.net",
"ns2.ddos-guard.net"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 54,
"malicious": 3,
"suspicious": 1,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"SOCRadar": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing (alphaMountain.ai)"
} |
| First seen | 2026-08-28T01:48:37Z |
| DNS records | [
{
"ttl": 3600,
"type": "A",
"value": "186.2.175.145"
},
{
"ttl": 3600,
"type": "SOA",
"rname": "support.ddos-guard.net",
"value": "ns1.ddos-guard.net"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns2.ddos-guard.net"
},
{
"ttl": 3600,
"type": "NS",
"value": "ns1.ddos-guard.net"
}
] |
| Dns at | 2026-10-13T09:09:33Z |
| Jarm | 2ad2ad16d2ad2ad22c41d41d000000d740f47fc623495ea334f7291b19b353 |
| Certificate | {
"san": [
"covabeans.co.kr"
],
"issuer": "Let's Encrypt / YR2",
"serial": "552fd8594171ac93b1cf911d055d14d74a5",
"sha256": "5a101fee5736d1158a7e22189be7378e631e96cccba5fa5304faec218b1cb2ed",
"subject": "covabeans.co.kr",
"valid_to": "2026-11-24T07:27:45Z",
"valid_from": "2026-08-26T07:27:46Z"
} |
No. PhishDestroy classifies covabeans.co.kr as a Gmail impersonation page (risk: critical, 81/100); it was first detected on 2026-09-27. VirusTotal: 3/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on covabeans.co.kr. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
ns1.ddos-guard.netns2.ddos-guard.netLocation describes the IP network.
5a101fee5736d1158a7e22189be7378e631e96cccba5fa5304faec218b1cb2edcovabeans.co.krSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.covabeans.co.krDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of covabeans.co.kr · checked Sep 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
covabeans.co.kr
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
redirected→live_content
content_served
Unknown→redirected
http_redirect
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content
content_served
1→Observation retained
0→1
Reachable
No threat flag
View source3/92 engine detections
View source4 community references
View sourcePD-20260927-96905D
Page captured
View sourcecovabeans.co.kr
View sourcePD-20260927-96905D Recipient: abuse@iqweb.io If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
covabeans.co.kr)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.