Which versions of secmeasure are malicious?

The following PyPI versions of secmeasure are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate secmeasure if I installed it?

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

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

Yes — secmeasure is associated with the 2025-08-secmeasure 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 secmeasure across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for secmeasure (3 malicious versions).

Malicious package

secmeasurePyPI

Advisory published Aug 3, 2025Updated Dec 31, 2025

secmeasure is a confirmed malicious PyPI package (MAL-2025-47452) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in secmeasure (PyPI)

MAL-2025-47452

Immediate action

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

pip uninstall secmeasure

What this malware does

This package installs the SilentSync remote access trojan and allows remote code execution and data exfiltration. Windows machines are targetted by this malicious package.

Calling a method starts downloading and starting an infostealer script

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

Campaign: 2025-08-secmeasure

Reasons (based on the campaign):

action-hidden-in-lib-usage
Downloads and executes a remote malicious script.
infostealer

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

f566db2e1359b455ca36524d9c066854754e71ac92deca9706f69d3d71cc8414

ebfd54accf25face6552daeb47eabe02bdc4e9486791bd3dbab41712db1a96f5

6358a31772627867b25a23822234b0bdbeb14cdaa939e3eeef0c5240ee36d86f

aa1a348d7da9310801f05ee32abd7500a4b0cce976ec41cf295a85fe601cdcfe

43bad55d7fc575031a37e72ea92eabca6e76507bbc57889afdadd7dada2bd62d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for secmeasure (3 malicious versions).
If you installed it — respond
secmeasure 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 secmeasure 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. secmeasure on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-secmeasure

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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