Which versions of pckg-sv are malicious?

The following PyPI versions of pckg-sv are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate pckg-sv if I installed it?

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

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

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

Malicious package

pckg-svPyPI

pckg-sv is a confirmed malicious PyPI package (MAL-2026-2627) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pckg-sv (PyPI)

MAL-2026-2627

Immediate action

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

pip uninstall pckg-sv

What this malware does

Code exfiltrates sensitive crypto wallet's files and sets up a keylogger trying to catch the password to the wallet

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

Campaign: 2026-04-pckg-sv

Reasons (based on the campaign):

crypto-related
keylogger
exfiltration-crypto
persistence

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

2ae45d504dadccaa437ebeaa729136ca7b38074149772b076c7abb34ab1e81f4

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

Campaign

2026-04-pckg-sv

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pckg-sv-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

Explore

All malware advisories How O3 detects malware Vulnerability database