AI-enabled scams are running about 4.5 times more profitable than traditional fraud, according to FBI data and industry research released this year. The FBI's Internet Crime Complaint Center logged 181,565 cryptocurrency-related complaints in 2025, with reported losses of $11.366 billion.
..." and then sections. The article ends with "" but there is also a meta description field that is empty. We need to provide a translated meta description. Since the original meta description is empty, we can either leave it empty or generate a Dutch meta description based on the content. The instructions say "Translate this article to Dutch (nl)." and then the JSON response includes "meta": {"description": "Translated meta description in Dutch"}. Since the original meta description is not provided (it's empty), we might need to create one. But the instruction says "ORIGINAL META DESCRIPTION:" is empty. So we can either leave it empty or create a Dutch meta description summarizing the article. Usually, we should translate the meta description if provided. Since it's not, we can either omit it or provide a Dutch summary. I think it's safe to provide a Dutch meta description based on the article's content. However, the instruction says "Translate this article to Dutch (nl)." and then the JSON structure includes meta. The original meta description is empty, so we can set it to an empty string or create a suitable one. To be safe, I'll provide a Dutch meta description that summarizes the article.
Now, let's translate the content. We need to translate the entire HTML content. The article has a title (h2) and several sections. We'll translate the text, keeping the HTML tags.
Key terms:
- AI-enabled scams: AI-gefaciliteerde oplichting? Or "AI-ondersteunde oplichting"? Common Dutch term: "AI-gerelateerde oplichting" or "AI-aangedreven oplichting". I'll use "AI-ondersteunde oplichting" or "AI-gedreven oplichting". Let's use "AI-gedreven oplichting" for "AI-enabled scams".
- Cryptocurrency: cryptovaluta or cryptocurrency. Usually "cryptovaluta" is Dutch. But "crypto" is common. I'll use "cryptovaluta" for formal.
- Phishing-as-a-service: "phishing-as-a-service" is often kept in English, but can be translated as "phishing als dienst". But it's a tech term, so maybe keep as "phishing-as-a-service" with explanation? Better to translate: "phishing-as-een-dienst" but that's awkward. Usually in Dutch tech articles, they use "phishing-as-a-service" as a term. I'll keep it as "phishing-as-a-service" but perhaps add a Dutch explanation? Since it's a proper term, I'll keep it in English but italicize? Actually, the instruction says "Use appropriate Dutch terminology for crypto/tech terms" – so we should translate if possible. "Phishing-as-a-service" is often called "phishing als dienst" in Dutch. I'll use "phishing-as-a-service" with a note? But to be natural, I'll use "phishing-as-a-service" as it's widely understood. Or "phishing-diensten" but that's not exact. I'll keep it as "phishing-as-a-service" since it's a specific term. Similarly, "wallet-drainer" – "wallet-drainer" is a term, maybe "portemonnee-drainer" but that's not common. I'll keep "wallet-drainer" as is.
- IC3: Internet Crime Complaint Center – keep as IC3.
- Elliptic: keep as Elliptic.
- Barracuda: keep as Barracuda.
- Operation Level Up: keep as Operation Level Up.
- Delphi study: "Delphi-studie" or "Delphi-onderzoek". I'll use "Delphi-onderzoek".
- Complaint numbers: "klachten" or "meldingen"? In context, it's complaints to IC3, so "klachten" is fine.
- Reported losses: "gerapporteerde verliezen" or "opgegeven verliezen".
- "4.5x more profitable" – "4,5 keer winstgevender" (Dutch uses comma for decimal).
- "crypto slice" – "crypto-deel" or "cryptogedeelte".
- "phishing campaigns" – "phishingcampagnes".
- "kits" – "kits" is fine, or "pakketten".
- "low bar for entry" – "lage instapdrempel".
- "outsized payoff" – "buitensporige opbrengst" or "onevenredig grote opbrengst".
- "field guide for defenders" – "handleiding voor verdedigers".
- "counterweight" – "tegenwicht".
- "cut potential losses" – "verminderde potentiële verliezen" or "beperkte potentiële verliezen".
- "seized or frozen" – "in beslag genomen of bevroren".
- "gap between losses and recoveries" – "kloof tussen verliezen en terugvorderingen".
- "trending better" – "een betere trend" or "beter in de trend".
- "found new gears" – "nieuwe versnellingen gevonden" – idiomatic? "in een hogere versnelling" or "nieuwe versnellingen hebben gevonden".
We need to translate the entire article. The article has a lead paragraph and then sections with h2 headings. We'll translate each paragraph.
Also, note that the original article has some repeated text and notes about word count. The final version we are translating is the one that starts with "
AI-enabled scams are running about 4.5 times more profitable than traditional fraud, according to FBI data and industry research released this year. The FBI's Internet Crime Complaint Center logged 181,565 cryptocurrency-related complaints in 2025, with reported losses of $11.366 billion.
" and then the sections. The article ends with "" but there is also a meta description field that is empty. We need to provide a translated meta description. Since the original meta description is empty, we can either leave it empty or generate a Dutch meta description based on the content. The instructions say "Translate this article to Dutch (nl)." and then the JSON response includes "meta": {"description": "Translated meta description in Dutch"}. Since the original meta description is not provided (it's empty), we might need to create one. But the instruction says "ORIGINAL META DESCRIPTION:" is empty. So we can either leave it empty or create a Dutch meta description summarizing the article. Usually, we should translate the meta description if provided. Since it's not, we can either omit it or provide a Dutch summary. I think it's safe to provide a Dutch meta description based on the article's content. However, the instruction says "Translate this article to Dutch (nl)." and then the JSON structure includes meta. The original meta description is empty, so we can set it to an empty string or create a suitable one. To be safe, I'll provide a Dutch meta description that summarizes the article.
Now, let's translate the content. We need to translate the entire HTML content. The article has a title (h2) and several sections. We'll translate the text, keeping the HTML tags.
Key terms:
- AI-enabled scams: AI-gefaciliteerde oplichting? Or "AI-ondersteunde oplichting"? Common Dutch term: "AI-gerelateerde oplichting" or "AI-aangedreven oplichting". I'll use "AI-ondersteunde oplichting" or "AI-gedreven oplichting". Let's use "AI-gedreven oplichting" for "AI-enabled scams".
- Cryptocurrency: cryptovaluta or cryptocurrency. Usually "cryptovaluta" is Dutch. But "crypto" is common. I'll use "cryptovaluta" for formal.
- Phishing-as-a-service: "phishing-as-a-service" is often kept in English, but can be translated as "phishing als dienst". But it's a tech term, so maybe keep as "phishing-as-a-service" with explanation? Better to translate: "phishing-as-een-dienst" but that's awkward. Usually in Dutch tech articles, they use "phishing-as-a-service" as a term. I'll keep it as "phishing-as-a-service" but perhaps add a Dutch explanation? Since it's a proper term, I'll keep it
