# MAL-2026-6998: Malicious code in higherlogic-ocfe (npm)


- **Type:** Malicious package
- **Package:** `higherlogic-ocfe` (npm)
- **Published:** 8 Jul 2026
- **Also known as:** GHSA-6c7j-c4j8-rgq3

## What is MAL-2026-6998?

MAL-2026-6998 is a malicious package in higherlogic-ocfe, published on 8 Jul 2026. 

### Official description

Package `higherlogic-ocfe@99.9.1` 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.

## What should I do about MAL-2026-6998?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6998 is a malicious package: higherlogic-ocfe (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6998/ (Markdown: https://insights.sbomify.com/MAL-2026-6998/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6998

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6998/
Summaries are generated and may contain mistakes; the official description above is the record.