Which versions of newpackagetest2025 are malicious?

The following PyPI versions of newpackagetest2025 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate newpackagetest2025 if I installed it?

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

If newpackagetest2025 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is newpackagetest2025 part of a known attack campaign?

Yes — newpackagetest2025 is associated with the 2023-12-valuent 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 newpackagetest2025 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for newpackagetest2025 (version 1.0.0).

Part of a larger attack: 2023-12-valuent published 17 malicious packages. See the full campaign →

Malicious package

newpackagetest2025PyPI

Advisory published Nov 30, 2024Updated Dec 12, 2025

newpackagetest2025 is a confirmed malicious PyPI package (MAL-2024-12313) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in newpackagetest2025 (PyPI)

MAL-2024-12313

Immediate action

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

pip uninstall newpackagetest2025

What this malware does

Packages either test the malicious behaviour, or actually download and run a simple remote script during the installation.

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: 2023-12-valuent

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.
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7e59254fb484e9ce91017696266cc02cf924dc6913419bb2a79d5d5a9ba9e2a2

bb87fd7186acc9af957e5155c0bfda87798fa733efdea43ff60f647c3eb439a0

848e46753ee7a652af171f768aca287c076b3b1c981d4a23fbe570e9735b071f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for newpackagetest2025 (version 1.0.0).
If you installed it — respond
newpackagetest2025 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 newpackagetest2025 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. newpackagetest2025 on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2023-12-valuent

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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