Skip to main content
MalwarePublished Updated

oem-agentic-shared (npm) · Malicious Code

Affects oem-agentic-sharedSource GCVE Database

0

Malicious package : remove oem-agentic-shared and rotate any secrets on hosts that installed it.

Data as of 12 Jul 2026, 09:18 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6095

What to do

Remove oem-agentic-shared from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npmoem-agentic-sharedAffected
  • =99.9.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f612eb2fa947323c936a0bb1becc602f0f837f9023edac22a945470566386a8c) 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. ## Source: ghsa-malware (e13b6880f6fcb8357aa28f079843c0f1296d6bb1be362258da49ea56b2a501e8) 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.

References

Community reviews

Loading reviews…