Issue #5174💬 AnsweredOpened June 9, 2023by tomsleeter0 reactions

GrapeJS.com homepage hacked / chained redirect malware

快速解答by tomsleeter

This is intermittent, I'm now getting grapejs.com homepage as expected

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 114.0.5735.110 (Official Build) (64-bit)

Reproducible demo link

https://grapejs.com *EDIT: This site / domain serves malware, it is missing the "s" in the real grapesjs.com domain

Describe the bug

Upon visiting grapejs.com homepage the browser is sent into a chain of redirects , ultimately on a malware S3 landing page that blows to full screen + audio + popup spam demanding payments.

Reproduced on subsequent visits / chrome incognito. Fairly confident it's not on my side

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (3)

tomsleeterJune 9, 2023

This is intermittent, I'm now getting grapejs.com homepage as expected

tomsleeterJune 9, 2023

Okay this was my mistake, I mis-typed the URL / domain name-- missing the "s" in grapesjs.com. Visiting URL grapejs.com is a bogus address with a bunch of malware / popups

I believe the incorrect domain redirects to grapesjs.com every other page load making this more confusing.

Closing this out, no issues with the main website.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @tomsleeter.

The issue with GrapeJS.com homepage hacked / chained redirect malware appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating an inconsistent state.

What to try:

  1. Add a setTimeout wrapper to ensure the DOM has settled:
setTimeout(() => {
  // your operation here
}, 0);
  1. Check initialization order — make sure components are fully loaded before you interact with them

  2. Use the editor's event system — listen to completion events:

editor.on('component:mount', (component) => {
  // safe to interact with component here
});

Recommended next steps:

  • Test with the latest GrapesJS version if you haven't
  • Provide a minimal reproducible example (CodeSandbox) — this helps the team identify the root cause faster
  • Include GrapesJS version, browser, and console errors in your report

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.