Which versions of newpackagetest2027 are malicious?

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

How do I remediate newpackagetest2027 if I installed it?

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

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

Yes — newpackagetest2027 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 newpackagetest2027 across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

newpackagetest2027PyPI

Advisory published Dec 25, 2023Updated Dec 12, 2025

newpackagetest2027 is a confirmed malicious PyPI package (MAL-2023-8767) 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 newpackagetest2027 (PyPI)

MAL-2023-8767

Immediate action

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

pip uninstall newpackagetest2027

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.

The OpenSSF Package Analysis project identified 'newpackagetest2027' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4cf97b6a86a63b80cb4c4b4fb5bb854a634ccfc3ec3368054ad703e8abe12f64

45ad7c064146e623ed47dabc0496cc9664ce9e1186759adcdc87f977ef9a4bd8

7c1e4acddbaeafd87b1cce82ddc1025a3e5abd4c285a2fd2e7fcff07d37d500e

31fa45f3317b16d4efa4678801fd1aca16e85f7b2fe30ca06b29325aa25dcbda

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for newpackagetest2027 (version 1.0.0).
If you installed it — respond
newpackagetest2027 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 newpackagetest2027 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. newpackagetest2027 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)
OpenSSF: Package Analysis · finder

Detect & block this

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