62

Did you block them with your script?

63

Had the same issue. Seems that lottie people fixed it up.

64

yes worked on mine

65

Bro how are you guys accessing your apps :face_holding_back_tears:

66

I added the original code you published above and it seemed to resolve it for me. Waiting for other people to confirm.

1 Like
67

status page is up

3 Likes
68

i had the original code work for a bit, but there is a 2nd initialization in the malicious code that caused to to relaunch so i had to had a 2nd observer. Make sure to add:

/* Hide by default */ w3m-modal { display: none !important; visibility: hidden !important; }
69

the author should have pinned the version in the url instead of loading the latest version every time. this way the plugin would have loaded the exact version that the author used when building and testing instead of the new compromised version.
Using the latest version is meant for development, not production.

1 Like
70

Hahaha yeah I mentioned that here

(or pin the version)

1 Like
71

I am still going through the topic :grin:

1 Like
72

I guess I feel slightly better that Bubble itself is compromised by the Canvas reliance :grimacing: :cry:

73

I’ve just added it. Waiting to see.

74

@ryan8 should we all be adding this? I had Lottie html code (which I’ve removed) and don’t have the other plugins mentioned in the thread but it has just shown up again.

If so where do I add this code?

75

go to the header in the general setting of bubble under the SEO section

76

Awesome! Thanks - this works (for now).

78

And add to the bottom of this then deploy?

Screenshot 2024-10-30 at 21.28.43
Screenshot 2024-10-30 at 21.28.43566×266 5.05 KB

79

I removed the lottie plugin and it solved it for me… not sure why others are saying it does not work for them.

80

Worked for me!! thank you!

81

yes the header section under the setting / seo tab