Stories

Tell HN: Unbounce Security Incident

Article news.ycombinator.com

Tell HN: Unbounce Security Incident

Got this email a bit ago:

We detected a security event that began on or about October 14, 2026 that may have resulted in the exposure of keys for Unbounce’s integration with third party applications. You are receiving this notice because your former Unbounce account was connected to one or more of these applications.

We are actively investigating this issue with the assistance of third-party security experts. We currently have no evidence of any misuse of the integration keys. Because your Unbounce account is no longer active, no action is needed within Unbounce. However, we strongly recommend that you immediately take the steps outlined below in any third-party applications you previously connected to Unbounce:

Customers with integration to Mailchimp: Customers should first disconnect Unbounce in Mailchimp under Integrations → Manage → Other connections, and regenerate any Mailchimp API key they created for Unbounce. Customers should review activity in their Mailchimp account since October 14 to identify any suspicious activity associated with the Unbounce integration.

Customers with integration to HubSpot: Unbounce rotated the integration keys for HubSpot integrations on October 20. Customers should review activity in their HubSpot instance between October 14 and October 20 to identify any suspicious activity associated with the Unbounce integration.

Customers with integration to Salesforce: On October 22, Unbounce rotated the credentials for its Salesforce connected app, which disconnected all existing Salesforce connections. We recommend that customers revoke the previous Unbounce connected app in Salesforce Setup → Connected Apps OAuth Usage. Customers should review activity in their Salesforce instance since October 14 to identify any suspicious activity associated with the Unbounce integration.

Customers with integration to AWeber: On October 22, Unbounce rotated its AWeber app credentials, which disconnected all existing AWeber connections. Customers should review activity in their AWeber account since October 14 to identify any suspicious activity associated with the Unbounce integration.

Customers with integrations to Marketo, Keap (Infusionsoft), Insightly, or Campaign Monitor: These integrations use API credentials that belong to the customer, so Unbounce cannot rotate them. Customers should generate new credentials in the vendor’s application and deactivate the credentials previously used with Unbounce. Customers should review activity in their instances for these applications since October 14 to identify any suspicious activity associated with the Unbounce integration.

Customers who have connected Zapier to Unbounce: Zapier connects to Unbounce through Unbounce’s API using OAuth. On October 22, Unbounce revoked all existing tokens for these connections. No further action is needed. Customers may remove Unbounce from My Apps in Zapier.

Customers who have connected other applications to Unbounce: Some other applications also connect to Unbounce through Unbounce’s API using OAuth. On October 22, Unbounce revoked all existing tokens for these connections. No further action is needed.

Customers who use the Unbounce WordPress plugin: The Unbounce WordPress plugin connects to Unbounce through Unbounce’s API using OAuth. On October 22, Unbounce revoked all existing tokens for the plugin. No further action is needed. Customers may deactivate and remove the plugin in WordPress admin.

Customers who have used an API key: No action is needed within Unbounce.

For reference, legitimate traffic typically comes from 50.19.99.184, 63.186.16.150, 18.196.144.222, and 18.195.113.15 for our webhooks and integrations.

We understand that this is a frustration and we sincerely regret causing an interruption of your work. If you require further information, please visit this documentation.

Sincerely, The Unbounce Team

Discussion 0 comments · 2 points · coderintherye · 18h
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.