What does the triple-equals malware do?

When imported, the package attempts to exfiltrate environment variables and basic user info Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-triple-equals Reasons (based on the campaign): - exfiltration-env-variables - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk. The OpenSSF Package Analysis project identified 'triple-equals' @ 10.0.1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of triple-equals are malicious?

The following PyPI versions of triple-equals are flagged malicious: 10.0.1, 10.0.2. Treat any of these as compromised.

How do I remediate triple-equals if I installed it?

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

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

Yes — triple-equals is associated with the 2025-07-triple-equals 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 triple-equals 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 triple-equals (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging triple-equals across your stack and pipelines.

Malicious package

triple-equalsPyPI

Malicious code in triple-equals (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6328

Immediate action

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

pip uninstall triple-equals

What this malware does

When imported, the package attempts to exfiltrate environment variables and basic user info

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

Campaign: 2025-07-triple-equals

Reasons (based on the campaign):

exfiltration-env-variables
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

The OpenSSF Package Analysis project identified 'triple-equals' @ 10.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

10.0.110.0.2

Indicators of compromise (SHA-256)

c846f6c307a90dd9e7c0b57cb3c04387a7eb559452bc9ca3a536e926070c37de

e934d82c0e83d5bd3c25a562cb51d2df7530cf74bcf8c56ae036ba8c279a5b13

d65cc69dec9f320438a4209e4c952480d78b96c779a019b6a09c04499b9e3edc

e1e25d28ab1b9124159ec1feb0a705755e95f4bcd6cbefdd2521f7ea1c836835

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

Campaign

2025-07-triple-equals

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks triple-equals-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