PhishDestroy first recorded boros--pendle.finance on 2026-07-23. Stored VirusTotal result: 8/92 engines flagged. Malicious: 6. Suspicious: 2. Analysis time (as stored): 2026-10-11 21:14 UTC. Retrieved (as stored): 2026-10-27 07:34 UTC. Listed by external blocklists: MetaMask, ScamSniffer, SEAL.
Page title: “Rewards | Boros”
More about the sources
Recorded security signals
Stored VirusTotal result: 8/92 engines flagged. Malicious: 6. Suspicious: 2. Analysis time (as stored): 2026-10-11 21:14 UTC. Retrieved (as stored): 2026-10-27 07:34 UTC. Listed by external blocklists: MetaMask, ScamSniffer, SEAL. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded boros--pendle.finance on 2026-07-23. Stored VirusTotal result: 8/92 engines flagged. Malicious: 6. Suspicious: 2. Analysis time (as stored): 2026-10-11 21:14 UTC. Retrieved (as stored): 2026-10-27 07:34 UTC. Listed by external blocklists: MetaMask, ScamSniffer, SEAL. Risk: critical (evidence score 100/100). Registrar: NiceNIC. Status: Registration hold recorded. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. Do not enter credentials or connect a wallet.
The domain boros--pendle.finance is currently active and has been identified as part of a generic phishing operation. Registration data shows the domain was created on July 22, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED, indicating a very recent deployment. DNS resolution points to the IP address 188.114.96.3, and the domain is served by Cloudflare nameservers kip.ns.cloudflare.com and meera.ns.cloudflare.com.
VirusTotal analysis records two detections out of ninety‑one scanning engines, confirming that at least a minority of security vendors recognize malicious behavior. The domain appears on a single security blocklist and has been explicitly blocked by the PhishDestroy service, reinforcing its classification as hostile. No additional contextual data such as page titles or SSL details are available at this time.
Defenders should immediately add boros--pendle.finance to network block lists, monitor traffic to the associated IP address, and consider applying sink‑hole techniques for the Cloudflare name servers. Continuous observation of newly registered domains using the same registrar or similar naming patterns is advised to detect potential campaign expansion.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Page code check by a separate monitor · 0 / 100 · 2026-07-23 18:20 UTC
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
0
Analyzed at
2026-07-23T18:20:03Z
Source timestamp
2026-07-23 20:20:03
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
boros--pendle.finance — Generic Phishing Report
AI description
The domain boros--pendle.finance is currently active and has been identified as part of a generic phishing operation.
AI summary
The domain boros--pendle.finance is currently active and has been identified as part of a generic phishing operation. Registration data shows the domain was created on July 22, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED, indicating a very recent deployment. DNS resolution points to the IP address 188.114.96.3, and the domain is served by Cloudflare nameservers kip.ns.cloudflare.com and meera.ns.cloudflare.com. VirusTotal analysis records two detections out of ninety‑one scanning engines, confirming that at least a minority of security vendors recognize malicious behavior. The domain appears on a single security blocklist and has been explicitly blocked by the PhishDestroy service, reinforcing its classification as hostile. No additional contextual data such as page titles or SSL details are available at this time. Defenders should immediately add boros--pendle.finance to network block lists, monitor traffic to the associated IP address, and consider applying sink‑hole techniques for the Cloudflare name servers. Continuous observation of newly registered domains using the same registrar or similar naming patterns is advised to detect potential campaign expansion.
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
Every stored field, with its source and date
Network Security Intelligence Registrar context
Registrar contextNiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
PhishDestroy rates boros--pendle.finance as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-07-23. Stored VirusTotal result: 8/92 engines flagged. Malicious: 6. Suspicious: 2. Analysis time (as stored): 2026-10-11 21:14 UTC. Retrieved (as stored): 2026-10-27 07:34 UTC. Listed by external blocklists: MetaMask, ScamSniffer, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is boros--pendle.finance safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on boros--pendle.finance. A confirmed blockchain transaction cannot be reversed.
What should I do if I used boros--pendle.finance?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-07-23
DOM Analysisanalyzed 2026-07-23score 88/1001 brand signal
Submitted URLhttp://boros--pendle.finance/
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Accountability draft Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
kip.ns.cloudflare.com
meera.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services
Valid from
2026-07-22 14:54:19
Valid until
2026-10-20 15:51:44
Hostname match
Yes
Validity
Stored certificate expired
Collection time
2026-07-23 19:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6558b3bfa99c710601d4a9e8454f9d6d3f98eb3c3ca9be931afa5c04603c6768Certificate names · 2 SANs
boros--pendle.finance
*.boros--pendle.finance
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Suspended by the registrar — The domain is on hold (clientHold) and no longer resolves
Technical details
Primary outcomeRegistration hold observedreason: Registrar clientHold95% confidence
AttributionNICENIC INTERNATIONAL GROUP CO., LIMITEDmechanism: Registrar clientHoldsource: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Registrar clientHold
RDAP registrationRegistrar clientHoldNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientHoldclientTransferProhibitedexpires 2027-07-22 15:41 UTCchecked 2026-11-22 07:47 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinelast reachable: 2026-08-02 22:14 UTCcurrent episode first observed: 2026-08-05 01:45 UTCobserved RIP window: 2026-08-02 22:14 UTC → 2026-08-05 01:45 UTC · 51.53hmidpoint estimate ≈ 2026-08-03 23:59 UTC · precision low · basis bounded
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.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 03:30 UTC.
Recorded events: 17. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain is on hold (clientHold) and no longer resolves
Time to First Unavailability
Hours from detection to the first unavailable observation: 312
Recorded activity
5 entries
Lifecycle
Domain registered
Added to PhishDestroy+24 h 41 min
VirusTotal analysis with detections+80 d 4 h
AlienVault OTX
4 community references
+24 d 2 h
VirusTotal
8/92 engine detections
+80 d 4 h
Wayback Machine
Page archived
+5 min
Added to PhishDestroy
boros--pendle.finance
same minute
URLScan
Page captured
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Report all
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Nothing matches. Clear the search or choose another filter.
penclle.financeLookalike lettersVariant of pendle.financeInternal reportA !ServFailNS !ServFailpendlme.financeInserted characterVariant of pendle.financeInternal reportA 104.21.53.103NS harley.ns.cloudflare.comendle.financeMissing characterVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.comepndle.financeSwapped charactersVariant of pendle.financeA 188.114.96.3NS evan.ns.cloudflare.comoendle.financeReplaced characterVariant of pendle.financeA 188.114.96.3NS kay.ns.cloudflare.comp.endle.financeSplit into subdomainVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.compandle.financeBit flipVariant of pendle.financeA 104.21.22.157NS ariella.ns.cloudflare.compebdle.financeReplaced characterVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.compedndle.financeInserted characterVariant of pendle.financeA 104.21.46.252NS ajay.ns.cloudflare.compeendle.financeRepeated characterVariant of pendle.financeA !ServFailNS !ServFailpemdle.financeLookalike lettersVariant of pendle.financeA 188.114.96.3NS kay.ns.cloudflare.compemndle.financeInserted characterVariant of pendle.financeA 104.21.88.142NS cloe.ns.cloudflare.com
Showing 12 of 36
Show 24 more
penddle.financeRepeated characterVariant of pendle.financeA 188.114.96.3NS anahi.ns.cloudflare.compendele.financeInserted characterVariant of pendle.financeA 188.114.96.3NS delilah.ns.cloudflare.compendie.financeLookalike lettersVariant of pendle.financeA 15.197.148.33NS ns23.domaincontrol.compendile.financeLookalike lettersVariant of pendle.financeA !ServFailNS !ServFailpendke.financeReplaced characterVariant of pendle.financeNS ns1.openprovider.nlpendle-finance.comVariantVariant of pendle.financeA 13.248.169.48NS ns1.afternic.compendlefinance.comVariantVariant of pendle.financeA 13.248.169.48NS ns1.afternic.compendlew.financeAdded characterVariant of pendle.financeNS ns1.openprovider.nlpendlr.financeReplaced characterVariant of pendle.financeA 104.21.23.206NS eric.ns.cloudflare.compendlw.financeReplaced characterVariant of pendle.financeA 104.21.61.181NS mark.ns.cloudflare.compendmle.financeInserted characterVariant of pendle.financeA 104.21.80.67NS nicolas.ns.cloudflare.compenfle.financeBit flipVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.compenmdle.financeInserted characterVariant of pendle.financeA 104.21.28.58NS cameron.ns.cloudflare.compensle.financeReplaced characterVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.compentle.financeBit flipVariant of pendle.financeA !ServFailNS !ServFailplendle.financeInserted characterVariant of pendle.financeA 104.21.71.115NS julissa.ns.cloudflare.compnedle.financeSwapped charactersVariant of pendle.financeA 104.21.50.149NS evan.ns.cloudflare.compoendle.financeInserted characterVariant of pendle.financeNS ns1.openprovider.nlpwndle.financeReplaced characterVariant of pendle.financeA 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.compzndle.financeReplaced characterVariant of pendle.financeA !ServFailNS !ServFailpendlea.financeAdded characterVariant of pendle.financeA 69.57.162.191MX mx1-hosting.jellyfish.systemsNS dns1.namecheaphosting.compendled.financeAdded characterVariant of pendle.financeA 188.114.96.3NS gloria.ns.cloudflare.compendlen.financeAdded characterVariant of pendle.financeA 188.114.96.3NS nick.ns.cloudflare.compendler.financeAdded characterVariant of pendle.financeNS ns1.openprovider.nl
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches3
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 boros--pendle.finance)
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
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 →
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.