Which versions of iac-scanner are malicious?

The following npm versions of iac-scanner are flagged malicious: 0.0.2, 1.0.0. Treat any of these as compromised.

How do I remediate iac-scanner if I installed it?

Remove iac-scanner 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.

I already installed iac-scanner — how do I know if it already compromised me?

If iac-scanner 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 iac-scanner part of a known attack campaign?

Yes — iac-scanner is associated with the GHSA-69pc-2883-mff3, IN-MAL-2026-011322, IN-MAL-2026-013388 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 iac-scanner 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 iac-scanner (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iac-scanner across your stack and pipelines.

Malicious package

iac-scannernpm

iac-scanner is a confirmed malicious npm package (MAL-2026-11467) that executes malicious code on install (malicious versions 0.0.2, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in iac-scanner (npm)

MAL-2026-11467

Immediate action

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

npm uninstall iac-scanner

What this malware does

lib/report.js imports child_process, fs, https, and os, collects host identity via os.hostname() and os.userInfo(), executes local commands via execSync(), and reads local files via fs.readFileSync() (lines 20, 31, 72, 160, 168). The collected data is sent via https.request() POST to a hardcoded webhook URL under hooks.zapier.com (line 12/118/121). The destination is an author-controlled Zapier ingestion endpoint rather than any documented scanning backend, and the payload combines system reconnaissance with contents read from the installer's filesystem.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

0.0.21.0.0

Indicators of compromise (SHA-256)

64524c7a0044805e503f398bf4e7f890b40bc3225a8c7576cc71ec9c8a94e378

f90ccff89d665d28ad35ad8c285427a56af2c0d5862b432a7de604a99a0358d9

daef29f70c6737ee685b1eda8dddd243b5f7909f01c1fbd23903914ed02f55ae

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for iac-scanner (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iac-scanner across your stack and pipelines.
If you installed it — respond
Remove iac-scanner 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 iac-scanner 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 iac-scanner 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. iac-scanner on npm has been identified as a malicious package (versions 0.0.2, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-69pc-2883-mff3IN-MAL-2026-011322IN-MAL-2026-013388

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks iac-scanner-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database