Which versions of api-feature are malicious?

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

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

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

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

Yes — api-feature 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-feature 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-feature (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-feature across your stack and pipelines.

Malicious package

api-featurePyPI

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

MAL-2026-2555

Immediate action

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

pip uninstall api-feature

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)

d2d6ce181ca33dae84d7f82c8720ad731f3667dcfa0cc5488616f0f25e886dd0

95a86b3b34e693c4d4c63388af6aecc013b1e7e16da45b1a6189959ad657cd58

c86a3079da8157aef32d5d4c4f2420239981a142fc1150eb0ac2e695be2779e9

98eeadd28f443f5d879bbcd7eaade847dd466e639159a157c8a8cf4d1e11ebc3

331f20e4013049472607be3e8887600f9a8d3cc70f289b6b85e3dece57dc2978

2ba231b1937a3fd9a108bffeb323b3c7bc661761a6ff64b4d701fb07ebfabfae

933d5d30242c6dc59beac2c0b9688ec0367a331f9d87b0acc9a339a3be54440c

1dd524ea6a4bc1b0a21dff26384ccb8dbed7380d21a3e8f9a6cce8270aec3b05

c1baafe2215ae32376f02fb1618200dfdb511e513a5108c39a299060a46f2fad

d3a16e156533684c864124cc8b1eb017741b950d34e36ea17850c27e5ec975ea

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-feature (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-feature across your stack and pipelines.
If you installed it — respond
api-feature 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-feature 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-feature 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-feature 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) · reporter

Detect & block this

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