sysnative Phishing account information, password and more. Blocks.

Status
Not open for further replies.
Hi Maki,

I'm not able to replicate this error in Chrome.

1) Which version of Chrome are you using? Please provide the full version number.

2) Can you take a screenshot of the page before submitting the reply, including your response? Ideally if you can provide a full screenshot of the entire page - please supply several screenshots if the page is too big.

3) Does this happen every single time you try to post, or does this happen only occasionally? e.g. 1 out of 3 posts, or less regular?

Please carry out a scan using the ESET online scanner and MBAM Anti-Malware below - please post the logs these tools generate.
Online Malware Detection | ESET
Malwarebytes | Free Cyber Security & Anti-Malware Software
 
Slimjet:
Version 16.0.8.0 (based on Chromium 61.0.3163.79) (Official version) (64-bit)

The error/block occurs every time I try to quote someone's post in the post and I will choose to preview the message.
 
Hi Maki,

Thanks for the info - please can you provide the other details requested as well?

I believe this is likely due to either an incompatibility or bug with the version of Slimjet you're using. The version you're using is the 4th oldest release, and is using an outdated version of Chromium as it's base.

Please can you update to the latest version of Slimjet and confirm if you still get the error? The latest version is 17.0.2, based on Chromium 63.

If you're still getting an XSS issue, it's likely our forum software does not currently support SlimJet. As this browser alters the webpage itself, it's possible that the way it is doing this is creating a broken code issue which the XSS Auditor then picks up as an XSS error.
 
Hi Maki,

Thanks for the info - please can you provide the other details requested as well?

I believe this is likely due to either an incompatibility or bug with the version of Slimjet you're using. The version you're using is the 4th oldest release, and is using an outdated version of Chromium as it's base.

Please can you update to the latest version of Slimjet and confirm if you still get the error? The latest version is 17.0.2, based on Chromium 63.

If you're still getting an XSS issue, it's likely our forum software does not currently support SlimJet. As this browser alters the webpage itself, it's possible that the way it is doing this is creating a broken code issue which the XSS Auditor then picks up as an XSS error.

A newer version is not always better than the latest version of the browser.
However, this error is occasional because it does not occur now. Some code causes this error.
No ESET or MBAM log is required because it does not detect any suspicious viruses. So why send an empty log? I have never had problems with this in my life because I have UAC VERY HIGH turned on, and other multi-level system security at the highest level, including Microsoft updates - all.
The problem only occurs with the sysnative website (sometimes)
 
We cannot troubleshoot further until you try the latest version of Slimjet (17.0.2).
 
Hi Maki,

To add to Stephen's post - For us to assist you, we need your cooperation in following our instructions.

I can't read your mind, so unless you provide logs or respond to the points in my previous post we can't help you any further.

The latest version of SlimJet contains multiple bugfixes. It's important to keep your browser up to date to ensure you have both the latest bugfixes and security patches.

To reiterate, SlimJet is not a supported browser here. This is a browser that makes unknown code changes to our website which we can't support. As a website we also rely on ads to pay our monthly server costs, and continuing to provide free support for users. We understand not everyone wants to see ads, however as we rely on these to continue running, SlimJet is not something we're intending to support.
 
I will not quote the answer.
I will not choose "Post view"
It should solve the problem. There is no other solution. It is not important.
 
Any potential security issue is important to us.

However, as you're unwilling to help us diagnose this issue, I will close this thread.
 
Status
Not open for further replies.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top