Which versions of karma-jasmine-sinon are malicious?

The following PyPI versions of karma-jasmine-sinon are flagged malicious: 2.1.1. Treat any of these as compromised.

How do I remediate karma-jasmine-sinon if I installed it?

Remove karma-jasmine-sinon from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed karma-jasmine-sinon — how do I know if it already compromised me?

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

Yes — karma-jasmine-sinon is associated with the RLMA-2025-03625 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 karma-jasmine-sinon across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for karma-jasmine-sinon (version 2.1.1).

Malicious package

karma-jasmine-sinonPyPI

karma-jasmine-sinon is a confirmed malicious PyPI package (MAL-2025-6532) that executes malicious code on install (malicious version 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in karma-jasmine-sinon (PyPI)

MAL-2025-6532

Immediate action

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

pip uninstall karma-jasmine-sinon

Malicious versions

1 flagged

2.1.1

Indicators of compromise (SHA-256)

d06255597d94d6d28c846823a580ff6f9e6bd44f7e82cdd6fa1b9bdb800ed87b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for karma-jasmine-sinon (version 2.1.1).
If you installed it — respond
Remove karma-jasmine-sinon from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If karma-jasmine-sinon 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. karma-jasmine-sinon on PyPI has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03625

Credits

ReversingLabs · finder

Detect & block this

O3 blocks karma-jasmine-sinon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database