Supply chain · npm · High

Critical: Malicious 'kijai' npm Package Compromises Systems

Threat Engine Auto-Feed · data current as of 2026-07-22

The npm package 'kijai' has been identified as malicious, leading to full system compromise upon installation. All secrets and keys on affected systems must be rotated, and the package removed, though full remediation may require further steps due to potential persistent compromise.

  • Package: npm / kijai
  • Affected versions: >= 0
  • Severity: critical
  • Reach: ~10/wk
  • Exposure: 60/100 (High)

What happened — Credential / secret theft

The 'kijai' npm package contains malware that, when installed, fully compromises the host system. This grants an external entity control over the affected computer.

How the attack works

This is a malicious package attack where a seemingly legitimate software component introduces harmful code into a system. Upon installation, the malicious code executes, establishing unauthorized access and control over the environment.

Who's exposed

Profiles most at risk

  • Development teams using npm
  • CI/CD pipelines that pull npm dependencies
  • Any organization with systems configured to install npm packages automatically

Conditions that increase exposure

  • Projects with unpinned dependencies that might pull the malicious package
  • Lack of lockfiles (e.g., package-lock.json) allowing arbitrary version resolution
  • Use of internal mirrors that do not vet package integrity
  • Automated build systems that install dependencies without manual review

Blast-radius scenarios

  • An attacker gains full control over the compromised system.
  • All secrets (e.g., API keys, credentials, tokens) stored on the system are exposed and can be exfiltrated.
  • The compromised system can be used as a pivot point for further attacks within the network.
  • Persistent malicious software may remain even after package removal, making full remediation challenging.

What to do (defensive)

Detect

  • Scan dependency trees for 'kijai' in all projects.
  • Monitor network traffic for unusual outbound connections from systems that install npm packages.
  • Review system logs for unexpected process execution or file modifications post-package installation.

Contain

  • Immediately isolate any system found to have 'kijai' installed.
  • Block network access for compromised systems to prevent further exfiltration or lateral movement.
  • Suspend all CI/CD pipelines that might install this package.

Remediate

  • Consider any system that installed 'kijai' to be fully compromised and rebuild from a trusted image.
  • Rotate all secrets and keys (e.g., API keys, SSH keys, user credentials) that were accessible from the compromised system, doing so from a different, trusted computer.
  • Remove the 'kijai' package from all dependency lists and package-lock files.
  • Implement strict dependency pinning and review processes for all third-party packages.

Frontier verdict — High

Prioritize immediate detection and isolation of systems with 'kijai' installed, followed by comprehensive secret rotation and system rebuilding due to critical compromise.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.