Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in next-locomotive-init

The npm package next-locomotive-init was found to contain malware. Installation or execution of this package results in full system compromise. All affected systems should be considered fully compromised and all secrets and keys rotated from a clean machine.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • next-locomotive-initnpm package

The npm package next-locomotive-init has been identified as containing malware. According to the GitHub Advisory (GHSA-v4q3-jmq9-q449), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nGiven the severity of the compromise, affected users should assume complete loss of confidentiality and integrity of any data or credentials on the affected system.

Indicators of compromise

Packages
  • next-locomotive-init

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a clean, uncompromised computer
  • Remove the next-locomotive-init package from all affected systems
  • Perform a full security audit and malware scan of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-v4q3-jmq9-q449 · GitHub Advisory Database

Cite this entry

"Malware in next-locomotive-init." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 20, 2026; last updated July 20, 2026. https://supplychainattack.org/incident/malware-in-next-locomotive-init-12jnjj

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. activecritical

    Malware in iot-kfh-s3

    The npm package iot-kfh-s3 contains malware that grants full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. containedcritical

    Malware in lambda-cloudwatch-cdk

    Malware was discovered in the npm package lambda-cloudwatch-cdk. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.

    npmCompromised package
  3. containedcritical

    Malware in s3-lambda-dynamodb-cdk

    Malware was discovered in the npm package s3-lambda-dynamodb-cdk. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different system.

    npmCompromised package
  4. containedcritical

    Malware in lwc-slds-lbc

    Malware was discovered in the npm package lwc-slds-lbc, resulting in full system compromise for any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.

    npmCompromised package