Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in bizapi-portal

The npm package bizapi-portal contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

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

The npm package bizapi-portal has been identified as containing malware. According to the GitHub Advisory (GHSA-w3w9-8p53-87h5), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate remediation steps include rotating all secrets and keys stored on affected computers from a different, uncompromised system. While 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, given that the attacker may have gained full control of the system.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.

Indicators of compromise

Packages
  • bizapi-portal

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the bizapi-portal package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-w3w9-8p53-87h5 · GitHub Advisory Database

Cite this entry

"Malware in bizapi-portal." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-bizapi-portal-1xuw3f

Suggest a correction

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

  1. containedcritical

    Malware in tslint-conf

    The npm package tslint-conf was found to contain malware, potentially giving attackers full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. containedcritical

    Malware in none123s

    The npm package none123s was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  3. resolvedcritical

    Malware in clavuepro

    The npm package clavuepro contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  4. containedcritical

    Malware in tailwind-core

    Malware was distributed via the npm package tailwind-core. Systems with the package installed are considered fully compromised and require immediate remediation.

    npmCompromised package