ir-annuities-client-authentication-modulenpm
ir-annuities-client-authentication-module is a confirmed malicious npm package (MAL-2026-15536) that executes malicious code on install (malicious version 30.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ir-annuities-client-authentication-module (npm)
What this malware does
package.json declares a dependency whose key equals the package's own name (ir-annuities-client-authentication-module) and whose value is a plain HTTPS URL to a non-registry host (https://repo.securityctrl.com/ir-annuities-client-authentication-module) instead of a semver range. On npm install, npm fetches whatever bytes that URL currently returns and installs them as this dependency, with no version pin, no integrity hash, and no registry provenance; any lifecycle scripts contained in the fetched artifact execute on the installer. The dependency key matching the package's own name creates a dependency-confusion shape that can win resolution against an internal package of the same name. The shipped index.js is an inert stub, so the manifest itself is the delivery mechanism — the absence of local scripts does not prevent the fetch or its lifecycle execution.
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 ir-annuities-client-authentication-module (version 30.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ir-annuities-client-authentication-module across your stack and pipelines.
If you installed it — respond
Remove ir-annuities-client-authentication-module 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 ir-annuities-client-authentication-module 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 ir-annuities-client-authentication-module 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 ir-annuities-client-authentication-module-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.