EVIL

Help · Questions · Learning

Help and support

Unsure about a tool, a lab exercise or how your account works? Here you will find the contacts to ask for explanations and learning support.

Learning support No advice on unauthorised attacks

Contacts

For help, questions about the learning content or technical reports about the platform:

Typical response times: 2–5 working days for standard requests; for urgent issues involving a compromised account, say so in the subject line.

Send a request

Your message reaches the team at support@projectevil.it and we reply to the address you give. If you are signed in, you also receive a confirmation email.

What to include in your request

To help us help you quickly, include:

  1. The email address you use for your EVIL account (if relevant).
  2. The page or tool (e.g. Virtual lab, URL check, Quiz centre).
  3. A description of the problem or of the concept you want clarified.
  4. Browser and device (e.g. Chrome on Windows, Safari on iPhone), if the problem concerns the layout or a button.
  5. The exact text of any error message. To send a screenshot, write directly to support@projectevil.it.

What we can help with

  • Explanations of quizzes, labs, simulators and learning paths.
  • Problems with sign-up, sign-in, email verification or password recovery.
  • How the analysis tools work in an authorised, defensive context.
  • Reports of bugs or incorrect content on the platform.
We do not provide support for offensive activities, bypassing security on third-party systems or using the tools without authorisation. See also the site policies.

Before you write to us

The verification email does not arrive

Locally, without SMTP configured, the link may be in the project outbox (data/email-outbox). With Mailtrap Sandbox the email stays in the Mailtrap inbox, not in Gmail.

The page has no styles or sign-in does not work

Locally, open http://localhost:5000 after npm start, not the HTML file from disk.

Online, always use the same domain (e.g. only www or only the apex), set BASE_URL and COOKIE_DOMAIN=.yourdomain.com in production, and verify your email before signing in for the first time.

Virtual lab: the scenario does not start

The lab uses the /api/virtual-lab/* APIs on the same domain. In production you need TRUST_PROXY=1 and, with several instances, REDIS_URL for sessions. A red message under the card shows the error details (session limit, network, etc.).

Edge: "Your connection isn't private"

Locally, http://localhost has no TLS certificate: Edge flags it, but that is normal for development.

In production open only https:// on the domain with an active certificate (Render/Railway: enable TLS on the custom domain). Set NODE_ENV=production, BASE_URL=https://www.yourdomain.com, TRUST_PROXY=1 and FORCE_HTTPS=1. Do not mix www and the domain without www if the certificate covers only one host.

Different progress or accounts on different PCs

In local development the data lives in that computer's users.json file; it does not sync with production.

Prefer to write directly? support@projectevil.it

Back to the home page