Skip to main content

Supply-chain alert triage

How an AI SOC triages malicious-package alerts: confirm the package is in use, find the commit that added it, check CI exposure, and ticket the fix.

Use case
Updated

The short answer

Supply-chain alert triage works out whether a flagged dependency is really in your code, how it got there, and what it could have reached. Cotool lists Socket alerts and runs supply-chain detections on ingested Socket data, then investigates the code in GitHub.[1][2]

The problem

Adversaries plant malicious code in popular open-source dependencies such as npm and pip packages, and in CI components such as GitHub Actions.[9]

A flagged package matters only if a repository actually resolves it, which Socket's full scans show.[10]

How an AI SOC handles it

  1. Read the alert

    The agent lists the Socket alert and the packages and repositories it names.[1][10]

  2. Confirm it's in use

    Socket full scans show the dependencies a repository resolved, so the agent can tell whether the flagged version is in use.[10]

  3. Find where it came from

    In GitHub, the agent reads the commit, blame, and pull request that added or bumped the package.[2]

  4. Check CI exposure

    If the package ran in CI, the agent checks what the job could reach. Cotool's example CI/CD Security Responder handled a fork pull request that attempted workflow secret access.[3]

  5. Ticket the fix

    The agent opens a Jira or Linear issue for the owning team, or a pull request that pins or removes the package.[2][4][5]

Example

List a Socket organization's full scanshttp
GET https://api.socket.dev/v0/orgs/{org_slug}/full-scans
Authorization: Bearer <organization token>

The call behind the in-use check. The token needs the full-scans:list scope; Socket also accepts the token as a Basic auth username with a blank password.[10][11]

What people approve

  • Fix pull requests go through review in your repository, like any agent or skill change synced from Git.[6]
  • Response agents cannot close an alert as True Positive. When an agent confirms malicious activity, it escalates the alert and a person closes it.[7]

How Cotool handles it

  • Cotool lists Socket.dev under Code & CI on its integrations page and reads the Socket blog as a threat intel source.[1][8]

Integrations used

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. GitHub integration (Cotool docs) · accessed November 16, 2026
  3. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  4. Jira integration (Cotool docs) · accessed November 16, 2026
  5. Linear integration (Cotool docs) · accessed November 16, 2026
  6. AI SOC (Cotool) · accessed November 16, 2026
  7. Alerts (Cotool docs) · accessed November 16, 2026
  8. Integrations (Cotool) · accessed November 16, 2026
  9. Compromise Software Dependencies and Development Tools, T1195.001 (MITRE ATT&CK) · accessed November 16, 2026
  10. Socket API tokens and scopes (Socket docs) · accessed November 16, 2026
  11. Authentication (Socket API) · accessed November 16, 2026

Related use cases

All use cases

Related reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo