Which versions of swiv are malicious?

The following PyPI versions of swiv are flagged malicious: 0.0.1, 0.3, 0.4, 4.0.0. Treat any of these as compromised.

How do I remediate swiv if I installed it?

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

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

Yes — swiv is associated with the GENERIC-standard-pypi-install-pentest 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 swiv 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 swiv (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging swiv across your stack and pipelines.

Malicious package

swivPyPI

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

MAL-2025-6897

Immediate action

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

pip uninstall swiv

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'swiv' @ 4.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

4 flagged

0.0.10.30.44.0.0

Indicators of compromise (SHA-256)

1a2fe48d275159bf6ebc366c414d768a03713ed4185ea7084f0f0e5f6fadcfa4

fad45d4a336f26f8dbc2d1815665ebb29cbe469468e4beaa55319945a9d8a755

ea8e3cad2100ef83e25d127552fdce0c90cc6581d0be3dc259cb2eccc1e5bd65

945d4a5f54e77ae66588b5b64aa30eb2627903bffcb72a3031b9c4b6b2122b43

34e5aabc93ae05e19c82eabacfef167a7e24faed1a494c54ec4fc5dcb832cae9

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks swiv-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