Which versions of feature-preserve-portrait-editing are malicious?

The following PyPI versions of feature-preserve-portrait-editing are flagged malicious: 99.6. Treat any of these as compromised.

How do I remediate feature-preserve-portrait-editing if I installed it?

feature-preserve-portrait-editing 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 feature-preserve-portrait-editing — how do I know if it already compromised me?

If feature-preserve-portrait-editing 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 feature-preserve-portrait-editing part of a known attack campaign?

Yes — feature-preserve-portrait-editing is associated with the 2024-11-byted-dast 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 feature-preserve-portrait-editing 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 feature-preserve-portrait-editing (version 99.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging feature-preserve-portrait-editing across your stack and pipelines.

Malicious package

feature-preserve-portrait-editingPyPI

Malicious code in feature-preserve-portrait-editing (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10822

Immediate action

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

pip uninstall feature-preserve-portrait-editing

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'feature-preserve-portrait-editing' @ 99.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.6

Indicators of compromise (SHA-256)

3d12e1f2812f416429ec66a435d699f705df272a9030be39bdff3501ba4f796f

062c5d11492deb1b935c0411559e9f86f4e440bea785ebee039415bbffc78a08

655ca5fa8c26583d141a0d6f86c0bca2e156cbad062d86ff11ec6827d2ac9cf7

ab42e201a8d0933cb648de6cba6718a6ed67810e39bb97c4542f3e62f307f3bb

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks feature-preserve-portrait-editing-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