Which versions of markitanalysis are malicious?

The following PyPI versions of markitanalysis are flagged malicious: 0.0.1, 0.1.0. Treat any of these as compromised.

How do I remediate markitanalysis if I installed it?

markitanalysis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed markitanalysis — how do I know if it already compromised me?

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

Yes — markitanalysis is associated with the RLMA-2025-01972, 2025-01-markitanalysis, RLUA-2026-00497 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 markitanalysis 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 markitanalysis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging markitanalysis across your stack and pipelines.

Malicious package

markitanalysisPyPI

Malicious code in markitanalysis (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2974

Immediate action

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

pip uninstall markitanalysis

What this malware does

If installed using source package, the package collects selected environment variables, including GITHUB_TOKEN if set, and sends to an external service. The package doesn't hide its actions at all, but there are already multiple different packages with the same code.

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

Campaign: 2025-01-markitanalysis

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-env-variables

Malicious versions

2 flagged

0.0.10.1.0

Indicators of compromise (SHA-256)

18531f9f237a5e62ca2df58868cc4b67ca096600e119e2de549de03078bc53b1

03e02ea1cd483a1827fe1bb9e76b1ee25b130d93f1771c621a7cfe07eb4793ad

0181af7442259bbe6dfbeec39c99bc62b711e38ec00c2ce460dc47162390c591

0ad61b77969396f45539edb8f8a72394bf14141922f165aeb0af4858aca24875

ccb7acf38e3c7df20d9e0b5bd52120e77ed9ea6e0c29ce58f5e2144718e71277

6e66bba612285b75bfd948b0e6695491d53f544145e6b5d146378def20d2b92f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for markitanalysis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging markitanalysis across your stack and pipelines.
If you installed it — respond
markitanalysis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If markitanalysis 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 markitanalysis 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. markitanalysis on PyPI has been identified as a malicious package (versions 0.0.1, 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-019722025-01-markitanalysisRLUA-2026-00497

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks markitanalysis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring