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

@higherlogic/ocfenpm

@higherlogic/ocfe is a confirmed malicious npm package (MAL-2026-6911) 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 @higherlogic/ocfe (npm)

MAL-2026-6911
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @higherlogic/ocfe

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.

The OpenSSF Package Analysis project identified '@higherlogic/ocfe' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

b12a43aa95319a766b8f9e0902338f11012546f1d553480d8c97d7039ad24f98
2bbd559291bd6c2d7889aebe011bb43bef61938171904f5c9ff378f33fd9e5e9

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 @higherlogic/ocfe (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @higherlogic/ocfe across your stack and pipelines.

  2. If you installed it — respond

    Remove @higherlogic/ocfe 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 @higherlogic/ocfe 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 @higherlogic/ocfe 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. @higherlogic/ocfe 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-m2wg-xw25-9g9c

References

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @higherlogic/ocfe-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.

Explore

@higherlogic/ocfe (npm) malicious package — MAL-2026-6911 | O3 Security