ancestralfoods.pe is a blocklisted domain detected by PhishDestroy on 2026-10-21. Risk: critical (88/100). Registrar: NIC.PE. Status: Last known active. Hosting: Red Cientifica Peruana. VirusTotal: 5/92 engines flag it. Do not enter credentials or connect a wallet.
PhishDestroy listed ancestralfoods.pe as a suspicious domain because five VirusTotal engines flagged it as malicious. When fetched on 2026-10-21 the site responded with HTTP 200 and the recorded title “Ancestral foods”, which is the same date it was first seen by PhishDestroy.
How the scam works
The classification relies on automated security‑engine labels that commonly indicate phishing, malware distribution or other malicious activity. No specific malicious behavior was observed on the page, so the exact technique cannot be confirmed.
Evidence
VirusTotal scans on 2026-10-12 and 2026-10-21 each reported five of 92 engines (alphaMountain.ai, Chong Lua Dao, Gridinsoft, VIPRE, Webroot) marking the domain malicious. Google Safe Browsing checked on 2026-10-21 and did not flag the site. urlscan captured the page on 2026-08-27, gave an overall clean verdict but its machine‑learning engine flagged it malicious with a score of 33; OTX listed three pulses referencing the domain as of 2026-10-21, and PhishDestroy’s internal blocklist marks it blocked while external blocklists showed zero hits on that date.
Infrastructure
The domain is registered through NIC.PE. DNS resolution returned the IP 161.132.57.235, which belongs to the Red Cientifica Peruana network in Peru, and the site is served behind Cloudflare using WordPress, WooCommerce, Elementor and related web technologies.
What to do
Visitors should avoid submitting credentials or personal data to the site; if they have already done so, they should change any associated passwords and monitor accounts for suspicious activity. Defenders can add ancestralfoods.pe to deny lists and review access logs for connections to the recorded IP.
No. PhishDestroy classifies ancestralfoods.pe as a blocklisted domain (risk: critical, 88/100); it was first detected on 2026-10-21. VirusTotal: 5/92 engines flag it. Treat the site as unsafe.
Is ancestralfoods.pe safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on ancestralfoods.pe. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used ancestralfoods.pe?
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.
DOM Analysisanalyzed Oct 21, 2026score 88/1004 brand signals
Submitted URLhttp://ancestralfoods.pe/
Favicon Hash
Observed page title
Ancestral foods
Automated brand references
FacebookInstagramWhatsAppYouTube
TLS Certificate
Issued by Let's Encrypt / YR1· stored validity ends in 62 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
161.132.57.235
Network ASN
AS3132
Organization
Red Cientifica Peruana
Observed location
Lima, PE
Server header
Apache
Nameservers 2
ns.rcp.net.pe
ns2.rcp.net.pe
Mail routing 1 MX record
ancestralfoods.pepriority 0
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YR1
Valid from
2026-09-25 04:43:22
Valid until
2026-12-24 04:43:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9065ee57e0584947ad71c9709e2a5093d8c9d5d09040cfff01eeba39fe197a4bCertificate names · 2 SANs
ancestralfoods.pe
www.ancestralfoods.pe
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-22 10:26:12 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-22 10:26:12 UTClast content: 2026-10-22 10:26:12 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Recorded subdomains3
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
libro.ancestralfoods.peDomain record
produccion.ancestralfoods.peDomain record
www.ancestralfoods.peDomain record
The original observation time is not recorded for these hostnames.
Technologies · 13 identified
W
WordPress
CMSBlogs
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
Underscore.js is a JavaScript library which provides utility functions for common programming tasks. It is comparable to features provided by Prototype.js and the Ruby language, but opts for a functional programming design instead of extending object prototypes.
Query Migrate is a javascript library that allows you to preserve the compatibility of your jQuery code developed for versions of jQuery older than 1.9.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
4 evidence signal groups linked0 stored notification recordsLast known active
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including ancestralfoods.pe)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
