Which versions of framework-zero are malicious?

The following npm versions of framework-zero are flagged malicious: 45.0.0. Treat any of these as compromised.

How do I remediate framework-zero if I installed it?

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

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

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

Malicious package

framework-zeronpm

framework-zero is a confirmed malicious npm package (MAL-2026-15500) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in framework-zero (npm)

MAL-2026-15500

Immediate action

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

npm uninstall framework-zero

What this malware does

package.json line 11 declares a dependency whose source is the bare HTTPS URL https://repo.securityctrl.com/framework-zero instead of a registry version range. On npm install this URL is fetched and installed, running any lifecycle scripts in the returned tarball, with no version pin and no integrity check. The dependency key equals the package's own name (framework-zero), a dependency-confusion shape where the manifest itself is the delivery mechanism, and the pinned version 45.0.0 is implausibly high for the name — consistent with a resolution-winning squat against an internal package. The host repo.securityctrl.com is unrelated to any npm registry and can serve arbitrary content that changes at any time after publish.

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

bfa0b9f3bb077648bf715ae13565ed44e67471548c98861bd5fb4d9472a3223b

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

Campaign

IN-MAL-2026-019086

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks framework-zero-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