Which versions of atlassian-exp are malicious?

The following PyPI versions of atlassian-exp are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate atlassian-exp if I installed it?

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

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

Yes — atlassian-exp is associated with the GENERIC-standard-pypi-install-pentest 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 atlassian-exp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for atlassian-exp (version 99.0.0).

Malicious package

atlassian-expPyPI

Advisory published Nov 26, 2025Updated Dec 3, 2025

atlassian-exp is a confirmed malicious PyPI package (MAL-2025-191475) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in atlassian-exp (PyPI)

MAL-2025-191475

Immediate action

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

pip uninstall atlassian-exp

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.

The OpenSSF Package Analysis project identified 'atlassian-exp' @ 99.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

a8eff0a6a170a0f178577774f1e72d4ea5cec1f7dc16b59d8d30c581f5706fce

1d89ecf51ffdbca5e5e101a7b730b4a5d6f1a46dda65a174b5b3d9b6ed07750f

802483ac3ec3749092037040a0a50ed9fa329232a832ac15fd5a0c692c42a9fd

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks atlassian-exp-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