Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in pino-sdk-v2

Malware discovered in the npm package pino-sdk-v2. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with pino-sdk-v2 installed or running
Ecosystems
Attack vectors
Affected entities
  • pino-sdk-v2

A malware-laden version of the npm package pino-sdk-v2 has been identified and published to the npm registry. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nAccording to the GitHub Security Advisory (GHSA-h6xh-3v8c-jhjf), the malware grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise. Full system remediation and security review is recommended.

Indicators of compromise

Packages
  • pino-sdk-v2

Remediation

  • Immediately remove pino-sdk-v2 from all systems
  • Rotate all secrets, API keys, and credentials from a clean, unaffected computer
  • Perform a full security audit and malware scan of all affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if compromise is confirmed
  • Monitor for any unauthorized access or activity on rotated credentials

Sources

  1. GitHub Advisory GHSA-h6xh-3v8c-jhjf · GitHub Advisory Database

Cite this entry

"Malware in pino-sdk-v2." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-pino-sdk-v2-rn7rip

Suggest a correction

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

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package