Which versions of api-analysis are malicious?

The following PyPI versions of api-analysis are flagged malicious: 0.0.8. Treat any of these as compromised.

How do I remediate api-analysis if I installed it?

api-analysis 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 api-analysis — how do I know if it already compromised me?

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

Yes — api-analysis is associated with the 2026-03-roboat-addition 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 api-analysis 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 api-analysis (version 0.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging api-analysis across your stack and pipelines.

Malicious package

api-analysisPyPI

Malicious code in api-analysis (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2556

Immediate action

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

pip uninstall api-analysis

What this malware does

During installation package downloads and runs a malicious executable. Likely continuation of 2026-03-rowrap.

The campaign is built over a malicious Roblox API wrapper. The roboat[.]pro (later robase[.]app) domain advertises a wrapper that is either directly malicious (as roboat collected in the campaign 2026-03-rowrap) or uses a malicious dependencies (like roboat-utils). New versions are published simultaneously with malicious dependencies and quickly removed. Another advertisement channel is https://github.com/Addi9000/roboat referencing two active contributors: https://github.com/Addi9000 and https://github.com/RoCruise

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

Campaign: 2026-03-roboat-addition

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
malware
clones-real-package

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

8ba11f1706dc7e5b86a76316bf4f8dbd6e7486d8ad8da568a6e6075ca8d0d75f

35329aae238cb1cb29e50188837ef77a26fe88249eb2966c747b8e8a29c851b4

c3bf88cef3ca699f69bada95749b40c4426c9a9c528e53c473698be88cbdc783

3f9522ad3d394d8919892bc622434e144e55fe72134500d55b2c980023211742

2ac3f86a0666dfd7d170a76cee1e9b21d73ee7ffded36557841b323db00ed113

15e1f62b1f0dc10308f25d06a0e883799ef543511ee78b16b245d58df1ec043a

1200875b37d69f95f9c7f1db0f245c53eec2d09f998e49f40b3fcd2ce3e84243

a88cd5bf70904925e42888cf27f4ebb75a708c684f534673cf1efbc254b5779d

c86c645213a248efb117512a811b0d15c334163058bec54301fe166d27572915

931ae56a181d59b6ee2970af87f335139bc71aca671bb51da5a44454e62e8936

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

Campaign

2026-03-roboat-addition

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks api-analysis-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