ing-feat-itsme-oidc-authenticationnpm
Advisory published Updated
ing-feat-itsme-oidc-authentication is a confirmed malicious npm package (MAL-2026-5780) that executes malicious code on install (malicious versions 99.9.1, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ing-feat-itsme-oidc-authentication (npm)
What this malware does
package.json declares a dependency ltidisafe sourced from a bare HTTPS URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.9.tgz) rather than a registry version range. On npm install, npm fetches and installs whatever tarball that URL returns, including any lifecycle scripts it contains, with no registry integrity check, no version pinning to an immutable registry artifact, and no publisher binding. The URL host is unrelated to any declared repository or publisher for this package, and the implausibly high package version (99.9.1) combined with a name resembling an internal/corporate scope (ing-feat-itsme-oidc-authentication) is consistent with a dependency-confusion lure that forces resolution to this package and then pulls attacker-controlled code from the off-registry URL. The declared package name and the single off-registry dependency are the entire published attack surface.
The OpenSSF Package Analysis project identified 'ing-feat-itsme-oidc-authentication' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for ing-feat-itsme-oidc-authentication (2 malicious versions).
If you installed it — respond
Remove ing-feat-itsme-oidc-authentication 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 ing-feat-itsme-oidc-authentication was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks ing-feat-itsme-oidc-authentication-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.