oem-agentic-sharednpm
oem-agentic-shared is a confirmed malicious npm package (MAL-2026-6095) 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 oem-agentic-shared (npm)
What this malware does
[email protected] 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.
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 oem-agentic-shared (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 oem-agentic-shared across your stack and pipelines.
If you installed it — respond
Remove oem-agentic-shared 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 oem-agentic-shared 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 oem-agentic-shared 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 oem-agentic-shared-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.