VirusTotal
2 / 92 engine detections
Ouvrir le rapportbioforce.digital : Domaine sur listes de blocage, détecté par PhishDestroy le 2026-10-23. Risque : élevé (66/100). Bureau d’enregistrement : Spaceship. Statut : Dernier actif connu. Hébergement : CloudFLARENET-EU. PhishDestroy a envoyé 1 signalement d’abus. VirusTotal : 2/92 moteurs le signalent. Ne saisissez aucun identifiant et ne connectez pas de portefeuille.
“BIOFORCE | AI Trading Platform | Official Website”
Domaine sur listes de blocage: bioforce.digital — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 2/92 (alphaMountain.ai, SOCRadar); URLScan…
L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.
2 / 92 engine detections
Ouvrir le rapportRapport d’analyse
Ouvrir le rapport1 community reference
Ouvrir le rapportRapport d’analyse
Ouvrir le rapportAucune menace signalée
Ouvrir le rapportCapture de la page
Ouvrir le rapportLes résultats reflètent l’heure de collecte de chaque source. Zéro détection ne garantit pas la sécurité. Les références OTX sont des publications de la communauté.
PhishDestroy threat report
PhishDestroy’s intake automatically listed bioforce.digital on 2026-10-23 after VirusTotal flagged the domain as malicious. The prior AI assessment recorded that the site claimed to be an “AI Trading Platform” offering automated bot tools and asked visitors for personal information, which aligns with typical fraudulent investment schemes. The recorded page title was “BIOFORCE | AI Trading Platform | Official Website” and the HTTP response returned 200 on the same date. No external blocklists listed the domain at the time of checking.
Fake AI‑trading platforms typically promise high returns through automated, AI‑driven strategies to lure users into depositing funds or sharing credentials. Victims are asked to create accounts and provide personal or financial details, after which the operators disappear with the deposits or use the information for further fraud. The scheme relies on the credibility of AI terminology and polished marketing to convince inexperienced traders.
VirusTotal scanned the domain on 2026-10-18 and recorded two detections: one malicious (SOCRadar) and one suspicious (alphaMountain.ai) out of 92 engines. Google Safe Browsing checked the domain on 2026-10-23 and did not flag it. URLScan captured the site on 2026-09-17, returned a clean overall verdict but its engine analysis marked it malicious with a score of 99 and relevant tags. Cloudflare Radar scanned the domain on 2026-10-23 and labeled it malicious under the malware category. OTX listed one pulse referencing the domain on the same day. PhishDestroy’s internal blocklist includes the domain, while external blocklists reported zero matches.
The domain was registered on 2026-08-18 through Spaceship, Inc., giving it an age of 66 days at first sight. It was observed pointing to Cloudflare‑served IP addresses such as 188.114.96.1 and used Cloudflare’s CDN and security services. The TLS certificate, issued by Google Trust Services, was valid from 2026-08-18 to 2026-11-16, and the authoritative nameservers were luke.ns.cloudflare.com and addilyn.ns.cloudflare.com.
Users should avoid entering any personal or financial information on bioforce.digital and, if they have already done so, change passwords on related accounts and monitor for unauthorized activity. Organizations should add bioforce.digital to web‑filter and DNS blocklists and review logs for connections to the recorded Cloudflare IPs. No wallet‑related remediation is required because wallet recommendations are disabled for this domain.
Observations enregistrées de la page, du réseau et des scanners, regroupées par source et heure d’observation.
Observé: · Retrieved:
| Uuid | 01a16746-ebda-7382-a8f6-203f6690855a |
|---|---|
| Final url | https://bioforce.digital/ |
| Statut | 200 |
| Redirigé | https-only |
| Redirects | [
{
"to": "https://bioforce.digital/",
"from": "http://bioforce.digital/",
"status": 307
}
] |
| Ip | 188.114.97.3 |
| Contacted domains | [
"cdnjs.cloudflare.com",
"challenges.cloudflare.com",
"cdn.jsdelivr.net",
"fonts.googleapis.com",
"static.cloudflare.com"
] |
| Contacted IP addresses | [
"104.18.94.41",
"104.18.95.41",
"104.17.208.5",
"142.251.14.95",
"104.17.24.14",
"188.114.97.3"
] |
| Asns | [
"13335",
"15169"
] |
| Countries | [
"US"
] |
| Document hash | 78a71102f5b6997c84373b890189c73ef2e14f47ae8240fc7fa2af37e01931d4 |
| Script hashes | [
"ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142"
] |
| Globals | [
"LANG_MSGS",
"ClientJS",
"_q2ndw",
"toggleTermsPopup",
"__tsGet",
"__tsNeedsClick",
"__tsShow",
"__tsReset",
"__lgBS",
"__cfQR",
"turnstile",
"__cfRLUnblockHandlers",
"__lgT0"
] |
| Cookies | [
"entry_url"
] |
| Tls | {
"san": [
"bioforce.digital"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "bioforce.digital",
"protocol": "QUIC",
"valid_to": "2027-01-14T14:51:01Z",
"valid_from": "2026-10-16T13:51:03Z"
} |
| Âge du domaine en jours | 65 |
| Apex age days | 65 |
| Tls age days | 6 |
| Validité TLS en jours | 90 |
| Requests | 20 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 99,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"content-security-policy": "default-src 'self'; img-src 'self' data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net https://challenges.cloudflare.com; style-src 'sel",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin",
"permissions-policy": "camera=(), microphone=(), geolocation=()",
"cross-origin-opener-policy": "same-origin"
} |
Observé: · Retrieved:
| Uuid | 24124f8c-e966-4d4e-91b5-df640b97fc41 |
|---|---|
| Final url | https://bioforce.digital/ |
| Statut | 200 |
| History | [
{
"url": "https://bioforce.digital/",
"status": 200
}
] |
| DOM structure hash | 12efbc8d35d169f86a976b169ba58163d587f3a3e91811780bffc7bc698e61ac |
| Document hash | 64f8350728a12e282ad4575ef9c2dc7e8a5bbab875c8bf2d3563d0e5da78ada4 |
| Phishing v2 | [
"phishing"
] |
| Risques du domaine | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| Enregistrements DNS | [
{
"name": "bioforce.digital",
"type": "A",
"value": "172.67.137.41"
},
{
"name": "bioforce.digital",
"type": "A",
"value": "104.21.7.183"
},
{
"name": "bioforce.digital",
"type": "AAAA",
"value": "2606:4700:3035::6815:7b7"
},
{
"name": "bioforce.digital",
"type": "AAAA",
"value": "2606:4700:3033::ac43:8929"
}
] |
| DNSSEC valide | false |
| Ip | 172.67.137.41 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
| Fiche d’enregistrement | {
"registrar": "Spaceship, Inc.",
"created": "2026-08-18T07:31:41Z",
"updated": "2026-08-23T07:32:24Z",
"expires": "2027-08-18T07:31:41Z",
"nameservers": [
"luke.ns.cloudflare.com",
"addilyn.ns.cloudflare.com"
]
} |
Observé: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 1,
"suspicious": 1,
"undetected": 35
} |
|---|---|
| Vendor labels | {
"SOCRadar": "phishing",
"alphaMountain.ai": "suspicious"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Suspicious (alphaMountain.ai)"
} |
| Vu pour la première fois | 2026-08-18T08:41:56Z |
| Enregistrements DNS | [
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "addilyn.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3035::6815:7b7"
},
{
"ttl": 21600,
"type": "NS",
"value": "luke.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3033::ac43:8929"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.7.183"
},
{
"ttl": 21600,
"type": "NS",
"value": "addilyn.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.137.41"
}
] |
| Dns at | 2026-10-18T01:54:24Z |
| Jarm | 27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6 |
| Certificate | {
"san": [
"bioforce.digital"
],
"issuer": "Google Trust Services / WE1",
"serial": "625b8066beae93a40e4175c26290feae",
"sha256": "9941c4ceb0c2b4932ae5619441abee433b62ec5c821618189e57aa78a300741e",
"subject": "bioforce.digital",
"valid_to": "2027-01-14T14:51:01Z",
"valid_from": "2026-10-16T13:51:03Z"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"last changed": "2026-08-18T08:22:23Z",
"registration": "2026-08-18T07:31:41Z",
"registrar expiration": "2027-08-18T07:31:41Z",
"last update of RDAP database": "2026-10-16T15:52:53Z"
},
"registrar": "Spaceship, Inc.",
"registrar_iana_id": "3862"
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Enregistrements CAA | {
"domain": "bioforce.digital"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_by": [
"CloudFlare Family"
],
"blocked_count": 1
} |
| Web archive observations | {
"last": "2026-10-23T05:19:45Z",
"first": "2026-10-23T05:19:45Z",
"changes": 0,
"days_archived": 1,
"avg_page_bytes": 41150
} |
| Crawler rules | {
"agents": [
"*"
],
"present": true,
"sitemaps": [
"https://bioforce.digital/sitemap.xml"
]
} |
| Sitemap | {
"present": true,
"url_count": 140
} |
| Titre de la page et métadonnées | {
"ogUrl": "https://bioforce.digital/",
"title": "BIOFORCE | AI Trading Platform | Official Website",
"ogType": "website",
"robots": "index, follow",
"ogTitle": "BIOFORCE | AI-powered trading platform",
"ogSiteName": "BIOFORCE",
"themeColor": "#0D1117",
"description": "BIOFORCE delivers AI-driven trading support, automated strategies, live market monitoring, and secure account access for today’s traders.",
"twitterCard": "summary",
"canonicalUrl": "https://bioforce.digital/",
"ogDescription": "BIOFORCE delivers AI-driven trading support, automated strategies, live market monitoring, and secure account access for today’s traders."
} |
| Trackers | {
"requests": 18,
"trackers": [
{
"name": "Cloudflare",
"company": "Cloudflare",
"country": "US",
"category": "Hosting",
"requests": 8
},
{
"name": "Google Fonts",
"company": "Google",
"country": "US",
"category": "Hosting",
"requests": 1
},
{
"name": "jsDelivr",
"company": "jsDelivr",
"category": "Hosting",
"requests": 1
}
]
} |
| Formulaires et contenu mixte | {
"no_sri": [
"https://static.cloudflare.com/beacon.min.js",
"https://challenges.cloudflare.com/turnstile/v0/api.js",
"https://cdn.jsdelivr.net/npm/clientjs@0.2.1/dist/client.min.js"
],
"third_party_scripts": 3
} |
| Statut | {
"up": true,
"code": 200,
"timings": {
"dns": 1,
"tls": 19,
"wait": 119,
"connect": 6,
"download": 12
},
"response_ms": 157
} |
| TLS connection | {
"alpn": "h2",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
80,
443,
8080
]
} |
| Carbon | {
"bytes": 134042,
"co2_grams": 0.0049,
"cleaner_than": 16
} |
| Dns server | {
"ns": [
{
"ip": "162.159.38.217",
"host": "addilyn.ns.cloudflare.com"
},
{
"ip": "108.162.193.200",
"host": "luke.ns.cloudflare.com"
}
],
"zone": "bioforce.digital"
} |
| Cookies | {
"cookies": [
{
"name": "entry_url",
"secure": true,
"same_site": "Lax"
}
]
} |
| Location | {
"ip": "2a06:98c1:3121::9",
"asn": "13335",
"org": "CloudFLARENET-EU",
"city": "London",
"country": "GB"
} |
| Ssl | {
"issuer": "Google Trust Services / WE1",
"subject": "bioforce.digital"
} |
| Enregistrements DNS | {
"A": [
"188.114.96.9",
"188.114.97.9"
],
"NS": [
"luke.ns.cloudflare.com",
"addilyn.ns.cloudflare.com"
],
"SOA": "{\"nsname\": \"addilyn.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418086287, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
"AAAA": [
"2a06:98c1:3120::9",
"2a06:98c1:3121::9"
]
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"header": "max-age=31536000; includeSubDomains; preload",
"message": "Site is compatible with the HSTS preload list!",
"compatible": true
} |
| HTTP security policies | {
"xFrameOptions": "SAMEORIGIN",
"referrerPolicy": "strict-origin",
"xXSSProtection": false,
"permissionsPolicy": "camera=(), microphone=(), geolocation=()",
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": "default-src 'self'; img-src 'self' data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflar",
"strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
"crossOriginOpenerPolicy": "same-origin",
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Firewall | {
"waf": "Cloudflare",
"has_waf": true
} |
| Get ip | {
"ip": "2a06:98c1:3120::9",
"family": 6
} |
| Redirects | {
"chain": [
"https://bioforce.digital"
]
} |
| Tech stack | {
"technologies": [
"jsDelivr",
"Cloudflare Turnstile",
"Cloudflare Rocket Loader",
"ClientJS",
"Priority Hints",
"Google Font API",
"Font Awesome",
"cdnjs",
"HSTS",
"Cloudflare",
"Open Graph",
"HTTP/3"
]
} |
| Page links | {
"internal_count": 11
} |
| HTTP headers | {
"headers": {
"server": "cloudflare",
"content-type": "text/html; charset=utf-8",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"content-security-policy": "default-src 'self'; img-src 'self' data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; font-src 'self' https:",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin",
"permissions-policy": "camera=(), microphone=(), geolocation=()",
"cross-origin-opener-policy": "same-origin"
}
} |
Non. PhishDestroy classe bioforce.digital comme Domaine sur listes de blocage (risque : élevé, 66/100) ; il a été détecté pour la première fois le 2026-10-23. VirusTotal : 2/92 moteurs le signalent. Considérez ce site comme dangereux.
Non. Ne connectez pas de portefeuille, ne signez pas de messages et n’approuvez pas de jetons sur bioforce.digital. Les sites de phishing demandent des autorisations (approve, setApprovalForAll, Permit2) qui permettent à l’opérateur de déplacer vos actifs, et une transaction confirmée ne peut pas être annulée.
Changez tous les mots de passe saisis sur ce site et activez l’authentification à deux facteurs. Si vous avez connecté un portefeuille ou signé quelque chose, révoquez les autorisations et transférez les fonds restants vers un nouveau portefeuille ; ne communiquez jamais votre phrase de récupération. Aide pas à pas : guide d’urgence.
Pour ce gTLD, le registraire ci-dessus opère dans le cadre d’un contrat d’accréditation de l’ICANN. Les liens ci-dessous renvoient au barème officiel des frais et aux recommandations de conformité en vigueur en matière d’abus du DNS.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
La réputation Edge-IP n’est pas attribuée à ce domaine.
addilyn.ns.cloudflare.comluke.ns.cloudflare.comLa localisation correspond au réseau IP.
9941c4ceb0c2b4932ae5619441abee433b62ec5c821618189e57aa78a300741ebioforce.digitalMétadonnées du certificat enregistrées. Les dates du certificat sans fuseau horaire sont affichées telles qu’enregistrées. Le chiffrement du transport n’établit pas que le site est digne de confiance.
Google PageSpeed Insights — audit des performances mobiles de bioforce.digital · checked Oct 23, 2026
Métadonnées de réponse horodatées conservées par la chaîne de collecte locale. Chaque valeur ci-dessous se rapporte à l’heure d’archivage affichée.
http://bioforce.digital/https://bioforce.digital/Content-Type: text/html; charset=utf-8CF-Cache-Status: DYNAMICCache-Control: public, max-age=296, s-maxage=2527, stale-while-revalidate=67278Server: cloudflareContent-Encoding: gzipsummary*h3=":443"; ma=86400public, max-age=296, s-maxage=2527, stale-while-revalidate=67278DYNAMICa4ee465b8f767a3b-FRAkeep-alivegzipdefault-src 'self'; img-src 'self' data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; font-src 'self' https://fonts.gstatic.com text/html; charset=utf-8same-originFri, 23 Oct 2026 05:17:20 GMT; rel=preload; as=style; crossorigin, ; rel=preload; as=style; crossorigin{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}camera=(), microphone=(), geolocation=()strict-origin{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=r7x7ok4%2FoFgJdPHcrLLRnZV0DmmxsE0%2BYQq8pSxFV9F5tjpoZjkM6uuISb5xw%2Bdu%2FIE%2FlPzO2znrdbZwCzkweivLWQIOGo4faaynIgdm9mTWbat271CpGxpfLrhTH1LsJ75u"cloudflaremax-age=31536000; includeSubDomains; preloadchunkedaccept-encodingnosniffSAMEORIGINValeurs conservées par le collecteur ; les valeurs longues peuvent être raccourcies lors de la collecte.
PD-20261023-8EDB4B
Page captured
Voir la source1 community references
Voir la sourceAucune menace signalée
Voir la source2/92 engine detections
Voir la sourcebioforce.digital
Voir la sourceComparez ce que reçoivent un navigateur et un robot d’exploration, et vérifiez la présence d’un routage de trafic Keitaro.
bioforce.digital
PD-20261023-8EDB4B Recipient: abuse@spaceship.com Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.
Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.
Template-based draft · optional AI wording assistance requires separate consent
Choisissez les étapes correspondant aux informations que vous avez communiquées. Conservez une copie de ce rapport avec vos propres documents.
Cessez d’utiliser le site suspect. Accédez au vrai service via son application officielle ou une adresse en laquelle vous avez déjà confiance.
Conservez les e-mails originaux, reçus, messages et captures d’écran en lieu sûr. Une chronologie factuelle aide l’autorité destinataire à comprendre ce qui s’est passé. IC3 evidence guidance ↗
bioforce.digital)Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.
Un signalement ne garantit ni la récupération des fonds ni l’ouverture d’une enquête, mais des données de transaction précises et transmises rapidement peuvent aider les autorités et les prestataires à retracer l’incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analyse des menaces à l'aide de listes de blocage stockées, de WHOIS, de DNS et de preuves d'analyse publique
Scanner maintenantSignalez les domaines suspects à notre base de données des menaces — protégez la communauté
SignalerRapports de phishing récents et changements de disponibilité observés
SurveillerSurveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif
Ce rapport réunit des captures de pages enregistrées, des données d’enregistrement et de réseau, des résultats de scanners et l’historique des signalements de PhishDestroy. Chaque source conserve sa propre date d’observation. Ouvrez le rapport d’une source pour consulter le résultat d’origine.
L’analyse assistée par AI a été rédigée le . Elle décrit les preuves disponibles à ce moment-là ; les vérifications ultérieures des sources peuvent évoluer.
Une capture documente ce qui était affiché. Un résultat d’analyse consigne l’évaluation de ce fournisseur au moment de sa vérification. Ni un certificat valide ni un résultat sans détection ne garantissent la sécurité.