Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

intuit-authznpm

intuit-authz is a confirmed malicious npm package (MAL-2026-15511) that executes malicious code on install (malicious version 55.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in intuit-authz (npm)

MAL-2026-15511
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall intuit-authz

What this malware does

package.json at line 11 declares a self-named dependency intuit-authz whose source is the bare HTTPS URL https://repo.securityctrl.com/intuit-authz instead of a semver range resolved through the npm registry. On npm install, npm fetches whatever bytes that URL currently serves and installs them, running any lifecycle scripts contained in the fetched tarball. The reference is unpinned, has no integrity hash, and points at a host unrelated to Intuit's published domains, so the operator of repo.securityctrl.com controls code executed on every installer's machine. The self-named key (intuit-authz declaring intuit-authz as a dependency) combined with a version number (55.0.0) implausibly high for a package under this name matches the dependency-confusion shape targeting an internal Intuit authorization package.

Malicious versions

1 flagged
55.0.0

Indicators of compromise (SHA-256)

68a4d159209bece0d5b390b92e1d7a9a10496022056de8da653ea5572acc8fe7

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove intuit-authz 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.

  3. Did it already run?

    If intuit-authz 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.

  4. How O3 protects you

    O3 blocks intuit-authz 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. intuit-authz on npm has been identified as a malicious package (version 55.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019071

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks intuit-authz-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.

Explore

intuit-authz (npm) malicious package — MAL-2026-15511 | O3 Security