Which versions of triple-equal are malicious?

The following PyPI versions of triple-equal are flagged malicious: 10.0.5. Treat any of these as compromised.

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

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

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

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

Malicious package

triple-equalPyPI

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

MAL-2025-41786

Immediate action

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

pip uninstall triple-equal

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.

Malicious versions

1 flagged

10.0.5

Indicators of compromise (SHA-256)

3af295af2e1c074bbbfdd898091118d0395e3a7038505133ea9ea749a69ac835

97aacaac044cf793b35b94f07e75dcc4630bffbed79654ecca534c9f545986be

10911ac4eed73695e2fe15b22983d481742de5688de5b3329d330daa2f88bba9

86fbc797e958853d27921b8eefcffe90bb215673de57aae08a214e8d1469d8b7

e2f4350b800871d807ec1689f3d15b8c5845d5cc17b730ea0f16fad1ddbb199f

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

Campaign

RLMA-2025-042842025-07-triple-equalsRLUA-2026-00837

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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