Member Avatar for Phuzzy_1

`1ph

and I need you guys to explait it into detailt

`

  • 3 Contributors
  • 2 Replies
  • 288 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by happygeek
Reverend Jim commented: Lazy -3
rproffitt commented: Not a bear. -3

Dani AI

Generated

There is no single piece of “anti‑virus maker” software — building an AV product is a systems project made from many tools, components, and practices. At a high level you need: a systems language for the engine (C/C++ or increasingly Rust), build tools and CI (git, CMake, MSBuild, Jenkins/GitHub Actions), debuggers and profilers (gdb/WinDbg), static/dynamic analysis tools (disassemblers, sandboxing/VMs, tracing), pattern/rule engines (YARA-style), and a secure update/telemetry backend. Those pieces combined become a scanner, behaviour monitor, and management/service infrastructure.

Core AV components to plan for and why they matter: a fast signature scanner for known threats; a heuristic/ML or rule-based layer for unknowns; a behavioural/blocking layer that watches process/file/network activity; an isolated emulator/sandbox for safe dynamic analysis; a quarantine/remediation subsystem; a secure updater and telemetry pipeline; and an installer/driver component for on‑access scanning where needed. Each has tradeoffs in complexity, performance, and risk.

A practical, low‑risk path: pick one OS to target, learn its process/filesystem/kernel model, and implement a tiny offline scanner first (hashes + simple rules). Study existing open source projects and rule formats, add a YARA‑style matcher, then evolve into behaviour hooks and an isolated dynamic analysis service. Use isolated VM labs (no snapshots shared with host, no shortcuts), test with benign samples, add robust logging, code signing, and encrypted update channels before any real deployment.

To : be specific about target OS, goals (research, product, integration), and your experience so people can give focused guidance. To and : good points about safety and legality — never run unknown binaries as Administrator/root on your main machine, and observe legal limits when handling malware samples.

Recommended Answers

All 2 Replies

Member Avatar for AssertNull

and I need you guys to explait it into detailt

Translation: "I want you to spend 100 times more time crafting a response for free that does not benefit you than the time I was willing to spend crafting the question. If you are willing to do this, I will reward you by creating a virus to infect your computer."

No.

I WILL provide you with some source code if you promise to run it only as Root/Admin and only on YOUR computer. Run it first. Then I'll explain what it does. It's the only way to learn.

Edited by AssertNull
Member Avatar for happygeek

I would suggest that you read the posting rules with an emphasis on the 'keep it legal' section. Then, come back and explain exactly what you are trying to do and what help you are after - within those parameters...

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.