Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @concerns/i18n

Malware discovered in the npm package @concerns/i18n. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @concerns/i18n

A malware incident was identified in the npm package @concerns/i18n, published as GitHub Advisory GHSA-rp2m-w359-5cqp on June 29, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation requires rotating all secrets and keys from a different, unaffected computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise.\n\nUsers should assume that removing the package alone is insufficient to fully remediate the compromise.

Indicators of compromise

Packages
  • @concerns/i18n

Remediation

  • Immediately isolate any system with @concerns/i18n installed from the network
  • Rotate all secrets, API keys, credentials, and authentication tokens from a different, unaffected computer
  • Remove the @concerns/i18n package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review system logs and access patterns for signs of unauthorized activity
  • Consider full system rebuild or replacement if critical infrastructure is affected

Sources

  1. GitHub Advisory GHSA-rp2m-w359-5cqp · GitHub Advisory Database

Cite this entry

"Malware in @concerns/i18n." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-concerns-i18n-ovk7gt

Suggest a correction

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

  1. activecritical

    Malware in @contentprod-authoring/block-manager

    Malware was discovered in the npm package @contentprod-authoring/block-manager. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malware in @webda-infra/search

    Malware was discovered in the npm package @webda-infra/search. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in @citi-icg-171632/citicms-repo-component

    The npm package @citi-icg-171632/citicms-repo-component contained malware that provided full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately.

    npmCompromised package
  4. activecritical

    Malware in @bscom/styling

    The npm package @bscom/styling contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package