Malware in @ms-ows/logging
Malware discovered in the npm package @ms-ows/logging. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @ms-ows/logging
A malware incident was identified in the npm package @ms-ows/logging, published as GitHub Advisory GHSA-46wp-9qm3-2vv4 on June 29, 2026.\n\nAccording to the advisory, any 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, uncompromised 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 any credentials, keys, or sensitive data on affected systems have been exposed and take appropriate defensive measures.
Indicators of compromise
- Packages
- @ms-ows/logging
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @ms-ows/logging package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review access logs and monitor for unauthorized activity on affected systems
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-46wp-9qm3-2vv4 · GitHub Advisory Database
Cite this entry
"Malware in @ms-ows/logging." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-ms-ows-logging-eye4ee
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - resolvedcritical
Malicious code in @velliajs/discord (npm)
@velliajs/discord, a malicious npm package masquerading as a discord.js clone, contained two hostile mechanisms: an unpinned private git dependency with embedded GitHub PAT enabling arbitrary code injection on install, and a hidden runtime kill-switch that gates bot functionality based on a remote allow-list. Two live GitHub Personal Access Tokens were hardcoded in the package.
npmCompromised packageMalicious commit - 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 - 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