Is "AVAP API Specs" on VS Code Marketplace Safe to Install?

Verified
AVAP Framework · vscode · v1.30.185

AVAP API Specs

Risk Assessment

Analyzed
100
out of 100
CRITICAL

31151 security findings detected across all analyzers

VS Code extension analyzed via package manifest and static code analysis

Severity Breakdown

0
Critical
7368
High
23771
Medium
12
Low
0
Info

Finding Categories

1000
Malware Signatures

YARA Rules Matched

18 rules(1000 hits)
postinstall crypto operations postinstall file manipulation postinstall file download postinstall system command postinstall network communication postinstall obfuscation EncryptionAlgorithmsWeak postinstall persistence mechanism credential env files postinstall environment access postinstall registry modification credential git credentials NoDisableSanitizeHtml NoUseWeakRandom UsingCommandLineArguments UsingShellInterpreterWhenExecutingOSCommands +2 more

About This Extension

AVAP API Specs

Detailed Findings

1000 total

YARA Rule Matches

18 rules

AI Security Report

AI Security Analysis: AVAP API Specs

Analysis generated: 2025-12-11T22:59:35+13:00
Model: gemini-3-pro-preview


Quick Facts

Property Value
UUID 7935bdd9-3703-55e3-8092-e39a455f6dfa
Type vscode
Version 1.30.185
Users 30
Risk Score 100.0/100 (CRITICAL)
Malware Detected ⚠️ Yes
Secrets Exposed ✅ No
Critical Vulns ✅ No

AI Analysis

Executive Summary

This extension represents a CRITICAL security threat and should be considered malicious. The analysis indicates that "AVAP API Specs" exhibits behaviors consistent with a sophisticated supply chain attack or a malware dropper. It contains thousands of signatures associated with malicious post-installation scripts, including attempts to establish persistence, obfuscate code, download external files, and access system credentials. The publisher is unverified, and the user count is suspiciously low. Immediate removal and incident response procedures are required for any system where this extension has been installed.

Threat Assessment

The security posture of this extension is non-existent; it appears to be an active threat vector.

  • Malicious "Postinstall" Behavior: The most alarming aspect is the prevalence of postinstall YARA matches. In the npm/VS Code ecosystem, "postinstall" scripts run automatically with the user's privileges immediately after the extension is downloaded. The findings indicate this extension attempts to:
    • Establish Persistence: (Finding #10) Modifying the system to ensure malicious code runs even after a reboot.
    • Download Payloads: (Findings #9, #11, #12) Fetching additional executable code or malware from the internet, likely bypassing initial static analysis.
    • Obfuscate Code: (Findings #5, #18) Deliberately hiding the logic of its scripts, a strong indicator of malicious intent.
  • Credential Theft: Finding #6 (credential_env_files) suggests the extension attempts to locate and read environment variable files (often containing API keys and secrets), which is unrelated to the stated function of viewing API specs.
  • Anomalous Volume of Findings: The presence of over 31,000 findings suggests the extension may be bundling a massive number of compromised dependencies or is acting as a container for a suite of attack tools.

Risk Justification

The calculated Risk Score of 100/100 is fully justified and accurate.

  • Severity of Indicators: The presence of persistence_mechanism and obfuscation alongside network_communication in an install script is the definition of a Trojan/Dropper.
  • Publisher Trust: The publisher "AVAP Framework" is unverified and has a generic name, typical of actors attempting to look legitimate to casual observers.
  • Impact: The combination of file manipulation and system command execution capabilities implies a total compromise of the host environment upon installation.

Key Findings

  • Persistence Mechanisms (Finding #10): The extension contains code designed to maintain access to the system across restarts, which is highly abnormal for a VS Code extension.
  • Obfuscated Install Scripts (Findings #5, #18, #23): The use of obfuscation in post-install scripts indicates an intent to hide malicious logic from security scanners and manual review.
  • External Payload Dropping (Findings #9, #11, #12, #15): Multiple signatures indicate the extension attempts to download files immediately after installation, likely fetching second-stage malware.
  • Credential Harvesting (Finding #6): The extension targets .env files or similar credential stores, posing an immediate risk of data exfiltration.
  • System Command Execution (Findings #1, #24): The extension executes shell commands directly on the host OS, granting it broad control over the developer's machine.

Recommendations

  1. Immediate Removal: Uninstall the extension immediately from all environments.
  2. Isolate and Re-image: Due to the "Persistence Mechanism" findings, simply uninstalling the extension may not remove the threat. Systems where this was installed should be considered fully compromised and re-imaged.
  3. Rotate Credentials: Because the extension attempts to access environment files (Finding #6), assume all secrets (API keys, AWS tokens, SSH keys) present on the affected machine are compromised. Rotate them immediately.
  4. Network Blocking: Block the domains/IPs associated with the 158 network findings at the firewall level.
  5. Audit Logs: Review system logs for any unauthorized outbound network connections or file system changes that occurred during the time the extension was installed.

Mitigation Strategies

There is no safe way to use this extension.
The risk is intrinsic to the installation process itself (post-install scripts). No configuration or sandboxing within VS Code can mitigate the risk of the install script executing malicious system commands. The only mitigation is strictly prohibiting its installation.

Confidence Assessment

Confidence Level: High (95%)
While the input states 80% confidence, the convergence of multiple high-severity indicators—specifically the combination of persistence, obfuscation, and credential targeting within post-install scripts—leaves very little room for benign interpretation. The probability of this being a false positive is negligible.


Disclaimer

This analysis was generated by an AI model and should be reviewed by security professionals. The findings are based on automated security scanning and may include false positives. Always verify critical findings manually before taking action.

Frequently Asked Questions