Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

owa-analytics-utilsnpm

Malicious code in owa-analytics-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3373
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall owa-analytics-utils

What this malware does

The package owa-analytics-utils was found to contain malicious code.

The OpenSSF Package Analysis project identified 'owa-analytics-utils' @ 99.9.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.9.0

Indicators of compromise (SHA-256)

6b195f7f4b8add77e943e32fc4e7f08ea50ae2dc1d0021cf2f2bc54c035331b5
644a42250298e29b58f2cfe75c1d362637e2c31f1a1ef9b9cfbe5d9ff0475fb8

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for owa-analytics-utils (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging owa-analytics-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove owa-analytics-utils 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.

  3. Did it already run?

    If owa-analytics-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks owa-analytics-utils before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. owa-analytics-utils on npm has been identified as a malicious package (version 99.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks owa-analytics-utils-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
owa-analytics-utils (npm) malicious package — MAL-2026-3373 | O3 Security