Which versions of document-inference are malicious?

The following PyPI versions of document-inference are flagged malicious: 0.0.0, 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate document-inference if I installed it?

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

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

Yes — document-inference is associated with the RLMA-2025-02569, 2025-05-sl4x01 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 document-inference 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 document-inference (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging document-inference across your stack and pipelines.

Malicious package

document-inferencePyPI

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

MAL-2025-3742

Immediate action

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

pip uninstall document-inference

What this malware does

Packages that seem to be created by a legit bug bounty hunter. Designed to look like created by different organisations, they contain a couple of data exfiltration (including all env variables) and potential remote code execution (though the URL seems not to serve any code).

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

Campaign: 2025-05-sl4x01

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables
impersonation

The OpenSSF Package Analysis project identified 'document-inference' @ 0.0.2 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

0.0.00.0.10.0.2

Indicators of compromise (SHA-256)

4dbb3f4bab26a0095d969efb7bd23845a0ab5683269ccb37f98fcaf285d845d3

19d942f1e9c7601342053fa29d7c79572f7f4062c66779427b5dc1fc3bd1d7f0

7f6121ccf7ad568310d096f3dfe660590ca61be0024897b1d6ba4e148fd93b5b

0519099776ddb5cbd1778fa5f043a1cad34d94d5116ae895120aba38608e7eb0

eb38a693e9340cfa5d8cc982cae8ad6d198923e93393eb3b3ba0f143c1bf9fda

fb77820b216161bb5e8b3ebd30be5a9c58cd0a1c888302c4cffe9f67f129d983

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

Campaign

RLMA-2025-025692025-05-sl4x01

References

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks document-inference-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