# MAL-2026-5780: Malicious code in ing-feat-itsme-oidc-authentication (npm)


- **Type:** Malicious package
- **Package:** `ing-feat-itsme-oidc-authentication` (npm)
- **Published:** 15 Jun 2026

## What is MAL-2026-5780?

MAL-2026-5780 is a malicious package in ing-feat-itsme-oidc-authentication, published on 15 Jun 2026. 

### Official description

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.

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

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-5780 is a malicious package: ing-feat-itsme-oidc-authentication (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-5780/ (Markdown: https://insights.sbomify.com/MAL-2026-5780/index.md)
```

## Sources

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

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