Member Avatar for caffiene_junky

I have recently downloaded Dev C++ software and have been exploring the different header files. I wrote this very simple program (it had like 35 characters total) and every time I go to compile it I get a "Found Virus" alert. The thing that really gets me is that this is a real virus according to my anti virus software. It is called NTRoot-G. Has anyone else had a problem like this?

If anyone wants I can copy the source code down.

  • 3 Contributors
  • 3 Replies
  • 191 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by caffiene_junky

Dani AI

Generated

Brief expert note: the behavior described in this thread—an AV alert that only appears when a trivial program is compiled—most often comes down to three possibilities. One is a heuristic or signature false positive: the generated binary happens to match a pattern the scanner flags. A second is an infected toolchain or IDE install, which rightly suggested checking. A third is an existing system compromise that alters build output; ’s offer to try compiling elsewhere is the right way to separate those causes. Because the source shown is minimal, a false positive is the likeliest outcome, but verification is essential.

Useful triage steps include updating antivirus signatures and rescanning the IDE and compiler install folders, producing the compiled EXE and scanning that file with an independent engine or a multi-engine service (mind privacy when uploading binaries), and compiling the same source on another machine or with a different toolchain. Re-downloading the IDE from an official source and verifying installer checksums isolates a corrupted distribution. Comparing scan results across engines quickly distinguishes a one-off false positive from something more serious.

Deeper analysis techniques that are helpful in this situation are building inside a clean VM or live environment, inspecting the generated binary’s metadata and imports with static tools, and testing whether tiny build changes (different output name, different flags) change the detection. If only a single engine flags the file, the odds favor a false positive; if multiple independent engines concur, treat it as higher risk and submit the sample to the vendor for analysis.

Final practical notes: if the toolchain proves infected, reinstall from an official, verified package and run a full system cleanup. If the detection is a false positive, request reclassification from the AV vendor and keep signatures current. The workflow above follows the sensible paths already suggested by and while avoiding unnecessary panic.

Recommended Answers

All 3 Replies

Member Avatar for kc0arf

Hello,

If you do not mind submitting the code, I'll try to compile it. I bet you have something else on your Windows (most likely) though. What are you using as an anti-virus software?

Christian

Member Avatar for caffiene_junky

The source code was this:


#include <stdlib.h>
int main()
{
}

I am using Mcafee anti virus. I dont think that it is a problem with the Software because it is only when I compile this one program. I can compile others and nothing has happened.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.