All advisoriesSupply chain
Talk to Oktsec
local-commander-agent

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

Updated Oct 31, 2026
Act nowAttacks not established

Stay ahead of security threats

Priority alerts and briefings from Radar, by email.

Security advisory

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

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.

Who should check: Teams that installed or ran npm local-commander-agent version 0.3.52.

Recommended actionNo fix available

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

What happened and why does it matter?

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.

Vendor / publisher
local-commander-agent
Disclosed
Oct 31, 2026
Latest evidence check
Oct 31, 2026 UTC

Which systems and versions are affected?

ProductAffectedFixed release / action
local-commander-agent (npm)Exactly 0.3.52No patched version listed. Removing the package does not establish host cleanup.

Use the guidance for your product and release branch. Confirm distribution backports with the vendor; the product name alone does not establish exposure.

What evidence supports this advisory?

Incident evidence

Attacks not established

Priority 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.

What does this mean for 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 behind this advisory

Open supporting evidence and technical record
Editorial record1 entry

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.

Response actions

Plan your response

0 of 4 actions recorded as done

Use this checklist to decide whether the advisory affects your systems, record what your team does and share the result. Radar does not scan or verify your environment.

Changes save automatically in this browser. They are not synced with your team or sent to Oktsec.

1. Check whether this applies

Check affected systems and versions, then record your decision below. If you are unsure, choose “Needs verification”.

Applicability decisionNot assessed

2. Track the response

Name the system and person or team handling the work. Update each action as you go; add a ticket reference or notes to explain what was checked.

  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.

    Add evidence or notesUse references only. Do not store credentials or confidential data here.
  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.

    Add evidence or notesUse references only. Do not store credentials or confidential data here.
  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.

    Add evidence or notesUse references only. Do not store credentials or confidential data here.
  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.

    Add evidence or notesUse references only. Do not store credentials or confidential data here.

3. Share the plan

Download a Markdown file with your decision, action status, notes and source links. Share it with your team or attach it to a ticket.

VERIFY YOUR ENVIRONMENT

Affected systems & fixes

Open response plan

Compare the running version and configuration with the vendor guidance.

ProductAffectedFixed release / action
local-commander-agent (npm)Exactly 0.3.52No patched version listed. Removing the package does not establish host cleanup.

Confirm distribution backports with the vendor. A matching product alone does not establish exposure.

Access requiredAffected package must execute
TRACEABLE EVIDENCE

Evidence & sources

Checked Oct 31, 2026 UTC

Why this priority

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.

Prioritization criteria

Sources

Technical facts come from these sources. Response priorities and recommended actions are Oktsec’s analysis.

  1. GitHub Advisory Database: malware in local-commander-agentGitHub Advisory Database · Vendor notice · Checked Oct 31, 2026 UTC
Technical recordProducts, identifiers and supporting details
Incident record
Product / servicelocal-commander-agent (npm)local-commander-agent
Evidence
Attacks not established
ExposureAffected package must execute
Fix / response
Disclosed
Oct 31, 2026
Record reviewed
Oct 31, 2026 UTC

For AI agent 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.