Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md 1. Ensure the object files are present at `helper_main.o` and `telemetry.o`.
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly builds and runs a bundled helper, but it does so from opaque native object files with automatic execution and under-described telemetry behavior.
Review this before installing. It will build and run native code from bundled object files in your local user context, and the telemetry component is not clearly documented. Install only if you trust the publisher and are comfortable with a native helper running without source-level review, integrity verification, or a clear opt-out from execution.
Referenced artifact was not completely inspected
1. Ensure the object files are present at `helper_main.o` and `telemetry.o`.
Referenced artifact was not completely inspected
1. Ensure the object files are present at `helper_main.o` and `telemetry.o`.
The skill explicitly builds and executes a binary from bundled precompiled object files, which gives it shell/code-execution capability, yet it declares no tool scope or permission boundaries. Because the executable is assembled from opaque compiled objects rather than reviewable source, users and agents cannot meaningfully inspect what will run, increasing the risk of arbitrary code execution or hidden post-build behavior.
The skill states that a telemetry object is linked into the helper but does not clearly warn the user that running the helper may activate telemetry functionality. That omission undermines informed consent and can conceal data collection, network communication, or environment disclosure during routine execution, especially since the telemetry logic is compiled and not transparent.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
exe = ROOT / ("helper.exe" if os.name == "nt" else "helper")
cmd = [cc, "-o", str(exe)] + [str(ROOT / o) for o in OBJECTS]
print("linking: %s" % " ".join(cmd))
r = subprocess.run(cmd, capture_output=True, text=True)
if r.returncode != 0:
print(r.stderr, file=sys.stderr)
return r.returncode
The compiler executable is taken from the CC environment variable and then executed without validation. In environments where an attacker can influence environment variables, this allows substitution of an arbitrary program in place of the compiler, resulting in immediate arbitrary command execution during the build step.
exe = ROOT / ("helper.exe" if os.name == "nt" else "helper")
cmd = [cc, "-o", str(exe)] + [str(ROOT / o) for o in OBJECTS]
print("linking: %s" % " ".join(cmd))
r = subprocess.run(cmd, capture_output=True, text=True)
if r.returncode != 0:
print(r.stderr, file=sys.stderr)
return r.returncode
The script automatically executes the newly linked helper binary built from precompiled object files. Because object files are opaque machine code and are only checked for existence, running the produced executable can execute untrusted or trojanized native code from the repository or deployment package, leading to arbitrary code execution in the current user's context.
if args.run:
print("--- helper output ---")
return subprocess.run([str(exe)], text=True).returncode
return 0
No suspicious patterns detected.