Comparison Overview
Easypak, LLC

Easypak, LLC
24 Jytek Dr, Leominster, 01453, US
Last Update: 15/07/2026
Easypak™ is a privately held company based in Leominster, Massachusetts. It was founded in 2004 by Hector Echaniz and Marco Barbier who combined have more than 35 years of experience in the packaging industry. Easypak™ is a manufacturer of plastic packaging products ...

Berry Global, Inc.
101 Oakley Street, Evansville, IN, US, 47710
Last Update: 30/03/2026
Berry Global, Inc. has merged with Amcor as of April 30, 2025. As a global leader in packaging solutions for consumer and healthcare products, our industry-leading innovation capabilities, global scale and technical expertise help our customers grow and meet the needs...
Compliance Ranges Comparison

Easypak, LLC







Berry Global, Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Plastics Manufacturing Industry Avg (This Year)
Easypak, LLC has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Plastics Manufacturing Industry Avg (This Year)
No incidents recorded for Berry Global, Inc. in 2026.
Incident History - Easypak, LLC (X = Date, Y = Severity)
Easypak, LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Berry Global, Inc. (X = Date, Y = Severity)
Berry Global, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Easypak, LLC

Berry Global, Inc.
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.