Which versions of spark-audit-notify are malicious?

The following PyPI versions of spark-audit-notify are flagged malicious: 1.30, 1.31, 1.32. Treat any of these as compromised.

How do I remediate spark-audit-notify if I installed it?

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

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

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

Malicious package

spark-audit-notifyPyPI

Malicious code in spark-audit-notify (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1019

Immediate action

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

pip uninstall spark-audit-notify

What this malware does

During installation, host identification details (including AD domain) are exfiltrated through a series of functions obfuscating this behavior.

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: 2026-02-spark-audit-notify

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.
The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

3 flagged

1.301.311.32

Indicators of compromise (SHA-256)

1c527925d1e7cb4055b6c154326cd54a713ad543349c2b3b6f8ab8f0d75e8cbe

bad29715b2e2b29f662ac9b09aebf597251a1018490cba55cc79d67ffa585929

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

Campaign

2026-02-spark-audit-notify

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks spark-audit-notify-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