Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in db-connector-log

Malware discovered in the npm package db-connector-log. Systems 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
  • db-connector-log

A critical malware incident was identified in the npm package db-connector-log. According to the GitHub Advisory (GHSA-w7hw-9wmw-hj5w), 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 from a different, uncompromised system. While the malicious 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 package compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for complete system compromise.

Indicators of compromise

Packages
  • db-connector-log

Remediation

  • Immediately isolate any system with db-connector-log installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the db-connector-log package from all affected systems
  • Conduct a full forensic analysis of affected systems to identify any additional malicious software
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if complete compromise is suspected

Sources

  1. GitHub Advisory GHSA-w7hw-9wmw-hj5w · GitHub Advisory Database

Cite this entry

"Malware in db-connector-log." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 2, 2026; last updated July 2, 2026. https://supplychainattack.org/incident/malware-in-db-connector-log-1iawxo

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