Which versions of ofjaaah-security-lib are malicious?

Every published version of ofjaaah-security-lib on npm is considered malicious. Remove the package entirely.

How do I remediate ofjaaah-security-lib if I installed it?

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

If ofjaaah-security-lib 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 ofjaaah-security-lib part of a known attack campaign?

Yes — ofjaaah-security-lib is associated with the GHSA-6vhq-9rv5-4fhh 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 ofjaaah-security-lib 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 ofjaaah-security-lib (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ofjaaah-security-lib across your stack and pipelines.

Malicious package

ofjaaah-security-libnpm

Malicious code in ofjaaah-security-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-344

Immediate action

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

npm uninstall ofjaaah-security-lib

What this malware does

The package ofjaaah-security-lib 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

f86f0b4e35deb1b768f59f036585665787b2ac5b62c23a0e49f0f3f675ea26e5

94bfbd5c89af01468786a4ff45da3126dbd49e28e4a250d0d124fc65b1f0c508

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 ofjaaah-security-lib (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ofjaaah-security-lib across your stack and pipelines.
If you installed it — respond
Remove ofjaaah-security-lib 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 ofjaaah-security-lib 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 ofjaaah-security-lib 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. ofjaaah-security-lib on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6vhq-9rv5-4fhh

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ofjaaah-security-lib-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