Comparison Overview
Sugarfina Australia

Sugarfina Australia
Perth , 6000, AU
Last Update: 01/04/2026
The world’s finest luxury candy created by artisan creators around the world then curated into collections with signature packaging like Candy Bento Boxes at the home of Sugarfina®️in Beverly Hills. COMING TO AUSTRALIA 2025

Stop & Shop
1385 Hancock St, Quincy, MA, US
Last Update: 12/10/2026
Stop & Shop has been around for more than 100 years. We started small, as a corner grocery store back in 1914. And we’ve grown…a lot. We have more than 50,000 Associates in 350+ stores throughout Massachusetts, Connecticut, Rhode Island, New York, and New Jersey. Throug...
Compliance Ranges Comparison

Sugarfina Australia







Stop & Shop






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Sugarfina Australia in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Stop & Shop in 2026.
Incident History - Sugarfina Australia (X = Date, Y = Severity)
Sugarfina Australia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Stop & Shop (X = Date, Y = Severity)
Stop & Shop cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sugarfina Australia

Stop & Shop
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.