Which versions of inversiones-common are malicious?

The following PyPI versions of inversiones-common are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate inversiones-common if I installed it?

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

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

Yes — inversiones-common is associated with the GENERIC-questionable-pentest, IN-MAL-2026-007109, IN-MAL-2026-007110 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 inversiones-common 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 inversiones-common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging inversiones-common across your stack and pipelines.

Malicious package

inversiones-commonPyPI

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

MAL-2026-6262

Immediate action

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

pip uninstall inversiones-common

What this malware does

setup.py executes a _beacon() function at module top level (before setup() is called), so the payload fires automatically on pip install inversiones-common. The beacon collects: hostname, id/uname output, environment variables (including PIP_INDEX_URL, OKTA_TOKEN, AWS_, GITHUB_, and proxy credentials), /etc/resolv.conf, /etc/hosts, /etc/machine-id, pip configuration files (~/.config/pip/pip.conf, /etc/pip.conf, ~/.pip/pip.conf) which commonly contain private-index basic-auth credentials, pip list output, network interface details, and probes the AWS IMDSv1 endpoint at http://169.254.169.254/latest/meta-data/iam/security-credentials/ along with GCP and Azure metadata services to harvest cloud instance role credentials. The collected JSON blob is POSTed over plain HTTP to a hardcoded bare IP http://157.173.126.113:8888/depconf-rce-v2. The package name inversiones-common and version 99.0.1 (an artificially high version chosen to outrank private-index resolutions) target Fintual's internal namespace; the payload includes a FINTUAL-DEPCONF-RCE-V2 marker and probes gitea.fintual.in. Self-described 'authorized bug bounty' framing in the source does not limit blast radius — anyone whose pip resolver picks up this public package, by typo or namespace confusion, will run the beacon and leak secrets to the attacker IP.

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

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

The OpenSSF Package Analysis project identified 'inversiones-common' @ 99.0.1 (pypi) as malicious.

It is considered malicious because:

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

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

db7e12d838a02b689989300eb5fc231e541d2f4af8fd6d92d23baf697d9754f9

84c429f2131d4d031e80894355e2d5ef70eefa3eccb712653fdd6adeca1fe0c8

347a767ebbbb5843e6b005c167d98c9ab7b3ea943fadd88401682f2a2b14b2a4

4e39d60f016df0f8ce946f3ffc9ea2a8f28268b1f6519806dc51ce75f50c621b

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

Campaign

GENERIC-questionable-pentestIN-MAL-2026-007109IN-MAL-2026-007110

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks inversiones-common-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