Which versions of @ms-ows/logging are malicious?

The following npm versions of @ms-ows/logging are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @ms-ows/logging if I installed it?

Remove @ms-ows/logging from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @ms-ows/logging — how do I know if it already compromised me?

If @ms-ows/logging was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @ms-ows/logging part of a known attack campaign?

Yes — @ms-ows/logging is associated with the GHSA-46wp-9qm3-2vv4, RLMA-2026-04761, RLUA-2026-05440 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ms-ows/logging across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ms-ows/logging (version 99.9.1).

Malicious package

@ms-ows/loggingnpm

Advisory published Jun 29, 2026Updated Jul 23, 2026

@ms-ows/logging is a confirmed malicious npm package (MAL-2026-6633) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ms-ows/logging (npm)

MAL-2026-6633

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ms-ows/logging

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

b7ffaf65611a7bb55512d442ab6d19f3b1c702db0224b994e0b80df4f30e1dff

ba032c561f30d14308c496aa86fe746faa2b9cda3f1a54b52baa21f0b71cc405

041b1a157ec538d197d5bff3e03629b8b5aafc5d0ac95f5e303ae669ed29a394

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @ms-ows/logging (version 99.9.1).
If you installed it — respond
Remove @ms-ows/logging from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @ms-ows/logging was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ms-ows/logging on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-46wp-9qm3-2vv4RLMA-2026-04761RLUA-2026-05440

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @ms-ows/logging-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database