# local-commander-agent 0.3.52 is malware: investigate affected hosts

Canonical: https://www.oktsec.com/radar/local-commander-agent-0-3-52
Publisher: Oktsec
Language: en
Published: 2026-10-31T12:46:55Z
Updated: 2026-10-31T12:46:55Z
Record reviewed: 2026-10-31T12:46:55Z
Latest evidence check: 2026-10-31T12:46:55Z
Disclosed: 2026-10-31

GitHub identifies npm local-commander-agent 0.3.52 as malware, with no patched version. If installed or run, treat the host as compromised and rotate secrets from a separate trusted computer.

## Evidence and response priority

- Category: Supply chain
- Oktsec priority: Act now
- Rationale: GitHub classifies this exact npm version as malware and advises treating hosts where it was installed or running as compromised. Removal alone cannot exclude persistence.
- Evidence: Attacks not established
- Verification: Single source
- Fix status: No fix available
- Exposure requirement: Affected package must execute
- Vendor: local-commander-agent
- Products: local-commander-agent (npm)

## Technical overview

GitHub’s October 31 advisory identifies exactly version 0.3.52 of the npm package local-commander-agent as malware. It lists no patched version. The advisory does not establish compromise of your organization or identify other package versions as malicious.

GitHub instructs users to treat a computer where this version was installed or running as fully compromised, rotate stored secrets and keys from another computer, and remove the package. Removing it cannot guarantee that additional malware or persistence is gone.

Oktsec recommends preserving evidence, investigating the affected host and reviewing credential use before restoring service. Check build workers, developer machines and agent execution environments only where installation or execution records establish applicability. Do not execute the package as a verification step.

## Recommended response

Isolate affected hosts, preserve evidence and rotate reachable secrets from a trusted computer; investigate before restoring service.

Relevant to: Teams that installed or ran npm local-commander-agent version 0.3.52.

## Affected systems and fixes

### local-commander-agent (npm)

Affected: Exactly 0.3.52

Fixed release / action: No patched version listed. Removing the package does not establish host cleanup.

Confirm the running version against the vendor advisory, including any distribution backports.

## Response checklist

1. **Locate installation and execution** — Check lockfiles, package caches, build records and installed versions for exactly 0.3.52. Do not install or run it to test exposure.
2. **Contain the host and preserve evidence** — Oktsec recommends isolating affected hosts and retaining package, process and authentication records before cleanup. Investigate persistence and determine whether a rebuild is required.
3. **Rotate secrets from a trusted computer** — Revoke and replace secrets and keys stored on affected hosts from a different trusted computer, then review their use. Do not perform recovery with credentials entered on the suspect host.
4. **Verify recovery before reuse** — Remove the package and complete host investigation or rebuild. Uninstallation alone is not evidence that other malware was removed. Validate restored access and record the recovery decision.

## Relevance to AI environments

If the package ran in an agent workstation or runner, inventory the credentials and tools accessible there. Its name alone does not establish that every AI environment is affected.

## Sources

- [GitHub Advisory Database: malware in local-commander-agent](https://github.com/advisories/GHSA-7j62-5j84-72fv) — GitHub Advisory Database; Vendor notice; checked 2026-10-31T12:46:55Z

## Editorial record

- 2026-10-31T12:46:55Z: Added the GitHub malware advisory for exactly npm version 0.3.52, with host investigation and secret rotation guidance. No patched version or organization-specific compromise is asserted.

## Related incidents

- [LiteLLM 1.107.0: check where it ran](https://www.oktsec.com/radar/litellm-1-107-0)

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/local-commander-agent-0-3-52) · [Build a response plan](https://www.oktsec.com/radar/local-commander-agent-0-3-52#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=local-commander-agent-0-3-52&service=exposure_check)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.