Which versions of configurator-framework are malicious?

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

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

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

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

Yes — configurator-framework is associated with the GHSA-wq4m-xvmv-ch8w 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 configurator-framework 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 configurator-framework (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 configurator-framework across your stack and pipelines.

Malicious package

configurator-frameworknpm

Malicious code in configurator-framework (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192381

Immediate action

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

npm uninstall configurator-framework

What this malware does

The package configurator-framework was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'configurator-framework' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

1af0aa1ec5b382702bc2719771ea888f78e59bbfae25976deab543815a731147

1415a36eca30ec625b99386cebfc5f9538d73854984673a1f6827c6f7db1ddac

00081d07df534b1b262b55665631e857c4b6e0c82ca9d466339f20ff095dd341

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 configurator-framework (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 configurator-framework across your stack and pipelines.
If you installed it — respond
Remove configurator-framework 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 configurator-framework 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 configurator-framework 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. configurator-framework 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

GHSA-wq4m-xvmv-ch8w

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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