Recurring Google Safe Browsing Warning – Possible Injected aes.js on My Website

Website URL

https://amelizschools.xo.je/

Error Message

Google Safe Browsing has repeatedly flagged my website for deceptive pages (social engineering).

The previous warning specifically identified:
https://amelizschools.xo.je/login.php?i=1

Google currently also blocks:
https://amelizschools.xo.je/aes.js

When I inspect the live source of login.php, I find an unexpected JavaScript reference to /aes.js. The script performs an AES-based calculation, sets a browser cookie, and redirects to login.php?i=1.

I cannot find aes.js anywhere in my hosting account.

Other Information

Hello InfinityFree Support Team,

I operate a PHP/MySQL school management system hosted on InfinityFree.

I have inspected my application files, including:

  • index.php
  • login.php
  • helpers.php
  • bootstrap.php
  • admin_header.php
  • admin_footer.php
  • admin.js
  • student_class_arms.js
  • attendance_actions.js
  • .htaccess

I have not found the AES challenge code in these files.

The live response from login.php contains:

The JavaScript sets a verification cookie and redirects to:

https://amelizschools.xo.je/login.php?i=1

However, I cannot locate aes.js in my htdocs directory or its subdirectories.

Please investigate and clarify:

  1. Is this JavaScript challenge generated by InfinityFree?
  2. Is the challenge injected by your hosting infrastructure?
  3. Has my hosting account experienced any compromise?
  4. How can I eliminate the cause of the recurring Google Safe Browsing warning?

I would appreciate your technical assistance in identifying the source of this behavior.
Thank you.

Welcome to the InfinityFree community forum! Good to have you here.

  • Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
  • Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
  • AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
  • Solving an issue is a joint effort. Try the suggestions you get and report back what happened.

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

Yes, the aes.js challenge comes from InfinityFree. It isn’t a compromise, and you won’t find the file in your htdocs because it isn’t part of your account. Our hosting puts a browser check in front of every free hosting site. A client that can’t run JavaScript and keep cookies gets a short HTML page that loads /aes.js, sets a cookie named __test, and redirects to the same URL with ?i=1 added. That is exactly what you describe, and the article says it can’t be turned off or excluded for a single file:

So your answers to questions 1–3 are: yes, it’s generated by us, yes, it’s injected by the hosting layer, and nothing in it suggests your account was hacked. Google’s scanner is probably seeing that challenge page when it fetches your URLs, which is why aes.js and login.php?i=1 appear in the listing. That’s why those are the URLs being named, but they’re probably not the cause of the flag.

For question 4, the fix goes through Google. We can’t remove a Safe Browsing listing, and Google doesn’t tell us why it flagged a site. This article covers the warning:

One reason on its list may fit you. A school management system with a login page, and possibly a login as the first thing visitors see, can be flagged when it acts on behalf of a school without saying so. The article’s advice for a legitimate site is:

  • Put a public homepage with real content in front of the login.
  • Say clearly who runs the site and which school it’s for.
  • Add contact details and a privacy policy.
  • Don’t use another organization’s name or logo unless the relationship is clear.

Then open the Security Issues report in Google Search Console and request a review once. Explain what the site is and what the login is for. The article suggests this even when the report shows no useful example URLs.

Does https://amelizschools.xo.je/ show a public page, or does it go straight to the login form? And does the Search Console Security Issues report list any examples besides those two URLs?

Website URL

https://amelizschools.xo.je

Error Message

My website, amelizschools.xo.je, has been flagged by Google Safe Browsing for Social Engineering / Deceptive Pages.
Google Search Console identifies these affected URLs:
/
/login.php
/login.php?i=1
/login.php?i=2
I have inspected my PHP application files, including login.php, bootstrap.php, helpers.php, config.php, index.php and .htaccess, but have not identified obvious malicious code.
Your forum previously confirmed that /aes.js is generated by InfinityFree’s hosting infrastructure.
Please investigate whether:
Any server-level scripts or injected resources are affecting my website.
The browser verification challenge could be interfering with Google’s Safe Browsing scanners.
There are any suspicious files, redirects or compromised resources associated with my hosting account.
Please help identify the actual source of the Google warning.
Thank you.

Other Information

Just help me find the cause.

Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.

The most likely cause isn’t a hidden file on your account. It’s what Google’s scanners see on the site itself. I can’t tell you what the /aes.js challenge is, because I didn’t find a source that says. I also can’t see your account’s files.

Our article on this warning lists the reasons Google flags a site as deceptive. Two of them match what you describe:

  • A student portal or learning platform for a school, or a site built for a client, that uses the organization’s name and asks visitors to log in. Google can flag this when it isn’t clear who runs the site.
  • A login form as the first thing visitors see, with no real public content in front of it.

The URLs Search Console lists are /, /login.php and its variants. That fits a site where the homepage leads straight to a login. The article also says the listed URLs are only a sample.

The article’s advice for a legitimate site is:

  • Add a public homepage that explains what the service does before anyone is asked to log in.
  • Say clearly who runs the site, with an about page and contact details. If it’s run for a school, say so, and add a privacy policy if you collect user data.
  • Use your own branding, not another organization’s names, logos or login designs.

After that, request a review once in Search Console. Explain what the site is, who runs it and what the login is for. Only Google can remove the listing, and we can’t do it for you.

The full steps are here:

One question would help here. Is amelizschools an actual school’s system that you run for them, or is it your own product? And does the homepage at / show anything besides the login?

Additional clarification – AMELIZ School Management System

Thank you for your response.

To clarify, AMELIZ School Management System is our own software product, developed and operated by AMELIZ. It is deployed for The Blessing of the Lord College, which is the school using the platform.

The school is not pretending to be AMELIZ, and AMELIZ is not impersonating the school.

I have updated the public homepage to explain this relationship, identify the school, identify AMELIZ as the technology provider, and provide visible access to the school portal.

However, Google Safe Browsing continues to block access to the website.

Could a human support representative please investigate whether any hosting-level behavior, injected content, or browser verification mechanism could be affecting Google’s assessment?

Thank you.

The security system isn’t the cause

Beyond that you’ll need to ask Google drive they are the ones who flagged your site. You have more information that we do

Also please read the below again

As far as we know, that’s not the case.

But as you should know by now: Google doesn’t say why exactly they flagged the website and URLs that they do. So we cannot say for certain one way or the other.

What doesn’t change regardless is that we cannot do anything about it for you right now.

So please read the guide again, and assess your site to the best of your abilities.

Or better yet, given that you’re already using AI, use it to help assess your website and fix potential issues.

When you’ve done all you can, just request a review and hope for the best.

Nobody can tell you exactly why your site has been flagged. Only Google knows and they don’t share. We cannot help you with this.