Which versions of oe-oauth are malicious?

The following npm versions of oe-oauth are flagged malicious: 99.99.1. Treat any of these as compromised.

How do I remediate oe-oauth if I installed it?

Remove oe-oauth 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 oe-oauth — how do I know if it already compromised me?

If oe-oauth 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.

Is oe-oauth part of a known attack campaign?

Yes — oe-oauth is associated with the GHSA-7724-j9h5-v5hg 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 oe-oauth across my projects, lockfiles, and CI pipelines?

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

Malicious package

oe-oauthnpm

Malicious code in oe-oauth (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-196

Immediate action

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

npm uninstall oe-oauth

What this malware does

The package oe-oauth was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'oe-oauth' @ 99.99.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.1

Indicators of compromise (SHA-256)

e75cae4824473b93438bf6a60c72ea18ad66368c8213af6bec6126171dead86e

c53c7a0c82b0a316878dbbd5767381ca0ef874192a308eb5001b953915dc816b

412d8ae25ded16fb507e7d120484a172ece322758c56fb4da2a6a7cd79b5be49

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for oe-oauth (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oe-oauth across your stack and pipelines.
If you installed it — respond
Remove oe-oauth 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 oe-oauth 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.
How O3 protects you
O3 blocks oe-oauth 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. oe-oauth on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7724-j9h5-v5hg

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks oe-oauth-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