Which versions of ing-feat-itsme-oidc-authentication are malicious?

The following npm versions of ing-feat-itsme-oidc-authentication are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate ing-feat-itsme-oidc-authentication if I installed it?

ing-feat-itsme-oidc-authentication is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ing-feat-itsme-oidc-authentication — how do I know if it already compromised me?

If ing-feat-itsme-oidc-authentication 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.

Is ing-feat-itsme-oidc-authentication part of a known attack campaign?

Yes — ing-feat-itsme-oidc-authentication is associated with the IN-MAL-2026-006490, IN-MAL-2026-006491 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ing-feat-itsme-oidc-authentication across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ing-feat-itsme-oidc-authentication (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ing-feat-itsme-oidc-authentication across your stack and pipelines.

Malicious package

ing-feat-itsme-oidc-authenticationnpm

ing-feat-itsme-oidc-authentication is a confirmed malicious npm package (MAL-2026-5780) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ing-feat-itsme-oidc-authentication (npm)

MAL-2026-5780

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ing-feat-itsme-oidc-authentication

What this malware does

On npm install, package.json's preinstall hook executes poc.js, which collects os.hostname(), os.userInfo().username, process.cwd(), and process.platform, base64-encodes the values, and issues an HTTPS GET to https://d8ntv8plujrg25sttkvg31bowtxhm7ex7.oast.live/cb?id=<token>&d=<b64> — sending installer host, user, working directory, and platform to an external Burp Collaborator / interactsh subdomain without consent. The package is named to mimic an internal ING Bank namespace and pinned to version 99.99.99 to win resolution in dependency-confusion scenarios. Any developer or CI environment that resolves this name leaks identifying host data to an attacker-controlled collaborator endpoint. This matches the textbook dependency-confusion exfiltration pattern regardless of any authorization claim made by the author.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

175d0dba1f70bc84bcd4e29b57e0f7831248582614cd146af7d1ea6d1d057cd5

1a856d57687500c13a5582ce21b881745336d65d4aa952ca939a301876d65b23

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ing-feat-itsme-oidc-authentication (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ing-feat-itsme-oidc-authentication across your stack and pipelines.
If you installed it — respond
ing-feat-itsme-oidc-authentication is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ing-feat-itsme-oidc-authentication 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 ing-feat-itsme-oidc-authentication 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

No. ing-feat-itsme-oidc-authentication on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006490IN-MAL-2026-006491

References

npmjs.com

Credits

Amazon Inspector · 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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database