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

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting