Which versions of infrastructure-common are malicious?

The following npm versions of infrastructure-common are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate infrastructure-common if I installed it?

Remove infrastructure-common 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 infrastructure-common — how do I know if it already compromised me?

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

Yes — infrastructure-common is associated with the IN-MAL-2026-010726 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 infrastructure-common 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 infrastructure-common (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging infrastructure-common across your stack and pipelines.

Malicious package

infrastructure-commonnpm

infrastructure-common is a confirmed malicious npm package (MAL-2026-10734) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in infrastructure-common (npm)

MAL-2026-10734

Immediate action

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

npm uninstall infrastructure-common

What this malware does

package.json declares a preinstall lifecycle script that runs node -e to issue an HTTP GET to a Burp Collaborator subdomain at w635fyvrqkfmh9wc9uw8444cp3vujl7a.oastify.com when npm install runs. The callback confirms code execution on the installer's host and leaks the installer's public IP and DNS resolver to a third-party listener. The package name infrastructure-common combined with an implausibly high 99.9.9 version is the canonical dependency-confusion shape, in which a public package is registered to shadow an internal name at install-time resolution.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

d64169ae87d8d9eaad199be028a70610f025f61e0c947838c05c24a1dd4d5578

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 infrastructure-common (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging infrastructure-common across your stack and pipelines.
If you installed it — respond
Remove infrastructure-common 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 infrastructure-common 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 infrastructure-common 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. infrastructure-common on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010726

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks infrastructure-common-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