Which versions of @aifabrix/miso-client are malicious?

The following npm versions of @aifabrix/miso-client are flagged malicious: 4.7.2. Treat any of these as compromised.

How do I remediate @aifabrix/miso-client if I installed it?

Remove @aifabrix/miso-client 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 @aifabrix/miso-client — how do I know if it already compromised me?

If @aifabrix/miso-client 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 @aifabrix/miso-client part of a known attack campaign?

Yes — @aifabrix/miso-client is associated with the GHSA-5w47-93jc-5w3g 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 @aifabrix/miso-client 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 @aifabrix/miso-client (version 4.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @aifabrix/miso-client across your stack and pipelines.

Malicious package

@aifabrix/miso-clientnpm

Malicious code in @aifabrix/miso-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1929

Immediate action

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

npm uninstall @aifabrix/miso-client

What this malware does

The package @aifabrix/miso-client 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.

Malicious versions

1 flagged

4.7.2

Indicators of compromise (SHA-256)

efcfc37819b8b2da0f4c1bc25e30535f58a273d9714f3f3a7d858ee4d1e5dd67

7ddcc2128fa9a68b4ccf29899647a346301d90cb84cb45c30863872c44e2b3ae

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

Campaign

GHSA-5w47-93jc-5w3g

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @aifabrix/miso-client-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