# MAL-2026-6095: Malicious code in oem-agentic-shared (npm)


- **Type:** Malicious package
- **Package:** `oem-agentic-shared` (npm)
- **Published:** 18 Jun 2026
- **Also known as:** GHSA-h957-h3mc-79qr

## What is MAL-2026-6095?

MAL-2026-6095 is a malicious package in oem-agentic-shared, published on 18 Jun 2026. 

### Official description

oem-agentic-shared@99.9.1 is a hollow stub: index.js exports an empty object and package.json has empty author, empty description, and no real functionality. Its sole effect on install is to pull in a single dependency declared as a direct HTTPS tarball URL — `ltidisafe` pinned to `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.0.9.tgz` — instead of an npm-registry version. The Google Cloud Storage bucket is not associated with this package's name and is not a known publisher CDN, so the tarball contents bypass npm-registry scanning entirely and any lifecycle scripts inside that tarball execute on `npm install`. The wrapper-plus-off-registry-tarball shape is a known smuggling pattern whose only purpose is to inject attacker-controlled, unscanned code into the installer's dependency graph.

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-6095?

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-6095 is a malicious package: oem-agentic-shared (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-6095/ (Markdown: https://insights.sbomify.com/MAL-2026-6095/index.md)
```

## Sources

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

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