Which versions of @axinom/mosaic-cli are malicious?

The following npm versions of @axinom/mosaic-cli are flagged malicious: 0.52.0-rc.2. Treat any of these as compromised.

How do I remediate @axinom/mosaic-cli if I installed it?

Remove @axinom/mosaic-cli 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 @axinom/mosaic-cli — how do I know if it already compromised me?

If @axinom/mosaic-cli 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 @axinom/mosaic-cli part of a known attack campaign?

Yes — @axinom/mosaic-cli is associated with the GHSA-726p-qgrh-hh53 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 @axinom/mosaic-cli 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 @axinom/mosaic-cli (version 0.52.0-rc.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @axinom/mosaic-cli across your stack and pipelines.

Malicious package

@axinom/mosaic-clinpm

Malicious code in @axinom/mosaic-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191450

Immediate action

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

npm uninstall @axinom/mosaic-cli

What this malware does

The package @axinom/mosaic-cli 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

0.52.0-rc.2

Indicators of compromise (SHA-256)

cd950f0ec7d4ffb3ef6c6d5e218b4178a873fbb76890b61b50bf7ccf82f8025a

7168f2a1e0e25128412330dd5022d955509346523f45c453d18e9205eb38b678

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

Campaign

GHSA-726p-qgrh-hh53

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @axinom/mosaic-cli-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