Threat LensFile scan report

Is agentrouter-local-proxy-v2.1.0.zip safe?

Verdict
Suspicious

ZIP archive shows process-injection and anti-analysis behaviour in sandbox but zero engine detections.

No antivirus engine flagged the sample, yet sandbox evidence includes T1055 process injection, T1485 data destruction, and T1562.001 defence-evasion techniques. Ten dropped children were clean and external-intel sources returned no hits. The combination of offensive MITRE techniques with zero detections places the file in mixed-signal territory.

Do not open or extract it until verified

Treat the archive as untrusted; do not run the contained scripts without strong isolation and monitoring.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 75 flagged
Flagged 0No detection 75
Digital specimenagentrouter-local-proxy-v2.1.0.zipea777f6094bcb0e79e…886f065a0896e1
Size31.0 KB
Code signingNot applicable
SandboxRuntime complete
First seen2d ago
Evidence3 priority signals
1 high-confidence signature or behavior rule matched this file.

Recommended next actions

01

Before opening or extracting

Do not open or extract it until the source can be verified independently.

02

If you already opened or extracted it

Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

55%Confidence
Moderate
Analyst conclusion

No antivirus engine flagged the sample, yet sandbox evidence includes T1055 process injection, T1485 data destruction, and T1562.001 defence-evasion techniques. Ten dropped children were clean and external-intel sources returned no hits. The combination of offensive MITRE techniques with zero detections places the file in mixed-signal territory.

Where this verdict could be wrong1 caveat
  • communityComments[0] contains researcher annotation 'Virus DO NOT TRUST WHAT HE SAY' — single unverified comment with 0 votes.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Treat the archive as untrusted; do not run the contained scripts without strong isolation and monitoring.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded
  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 22MITRE ATT&CK techniques
  • 15spawned processes
  • 0network contacts
  • 23filesystem & mutex artifacts

What this file does

Observed actions and their security significance

  • High concern: Injected code into another process, a technique that can conceal execution.

  • High concern: Attempted to impair or bypass security controls.

  • High concern: Manipulated how the operating system loads code, which can redirect execution.

  • Moderate concern: Contained obfuscated or packed code that makes inspection harder.

  • Moderate concern: Runs hidden system commands (script or shell).

  • Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.

  • Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.

These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

We couldn't fully clear this file. Treat it with caution.

  1. Recovery step 01

    Don't open or extract it unless you're certain it came from a source you trust.

  2. Recovery step 02

    Check where you got it — an unexpected attachment or a random download link is a red flag.

  3. Recovery step 03

    If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.

  4. Recovery step 04

    If you're still unsure, scan it again in a day or two — detections often catch up on newer files.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

7 evidence-based answers
Is agentrouter-local-proxy-v2.1.0.zip safe, or is it malware?
Evidence-based answer
agentrouter-local-proxy-v2.1.0.zip is suspicious — treat it as unsafe until you're sure. No antivirus engine flagged it; the cautious verdict comes from other saved evidence such as identity, prevalence, signing, or runtime signals. Don't open or extract it unless you fully trust where it came from. Get a fresh copy from the original trusted source and verify its exact hash when possible.
What is agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
agentrouter-local-proxy-v2.1.0.zip is a compressed archive, about 31 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
How many antivirus engines detected agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
None — 0 of 75 antivirus engines flagged agentrouter-local-proxy-v2.1.0.zip. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What should I do if I already opened or extracted agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
To remove agentrouter-local-proxy-v2.1.0.zip: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this archive from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What is the SHA-256 hash of agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
The SHA-256 hash of agentrouter-local-proxy-v2.1.0.zip is ea777f6094bcb0e79eeec032d1c32b5b91bff7a44ce6be717b886f065a0896e1, and its MD5 is 23f646b6bdad2c36bac2951269dee6fb. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of agentrouter-local-proxy-v2.1.0.zip?
Evidence-based answer
This report reflects the scan run on August 15, 2026. Because a file's hash never changes, the identity of agentrouter-local-proxy-v2.1.0.zip is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.