higherlogic-ocfenpm
higherlogic-ocfe is a confirmed malicious npm package (MAL-2026-6998) 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)
What this malware does
Package [email protected] is a dependency-confusion lure targeting the Higher Logic vendor namespace. The published index.js is an empty module.exports = {} — the package ships no functionality. Its sole dependency is declared in package.json as a direct tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.1.4.tgz) rather than a registry-hosted version. On npm install, npm fetches that tarball from an arbitrary Google Cloud Storage bucket and executes any lifecycle scripts it contains on the installer's machine. The high version 99.9.1 is the standard dependency-confusion pattern used to override an internal private package of the same name during resolution, and the bucket path segment depenconf reinforces the attack intent. The installer cannot audit the fetched bytes via normal registry tooling, and the tarball contents are mutable at the bucket owner's discretion.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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.
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.
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.
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
Campaign
References
Credits
- Amazon Inspector · 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.