Which versions of jamasp are malicious?

The following PyPI versions of jamasp are flagged malicious: 1.0.1.dev0. Treat any of these as compromised.

How do I remediate jamasp if I installed it?

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

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

Yes — jamasp is associated with the RLMA-2025-00477, GENERIC-standard-pypi-install-pentest, RLUA-2026-00438 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 jamasp 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 jamasp (version 1.0.1.dev0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jamasp across your stack and pipelines.

Malicious package

jamaspPyPI

Malicious code in jamasp (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-937

Immediate action

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

pip uninstall jamasp

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.

Malicious versions

1 flagged

1.0.1.dev0

Indicators of compromise (SHA-256)

75656b4c6ba88b69a3458dac19f1793e029a66d29498ce61e8ee3bd7dbf7801c

712e31607c90fb311b839af275ce1ad9dfe5a8ceb338d00b9094da22e66232fc

25cefd0eb9561401dbc711a241f7379bfca98d832180533aa96c96fa3e84f53b

5f658f1db89dfe972b7f069f1d08d536719181499a613ec1554de6d756e001cc

77345f78c559724e21f6d145a39468e2800f1389d0fe21456389d55e2e18cd95

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

Campaign

RLMA-2025-00477GENERIC-standard-pypi-install-pentestRLUA-2026-00438

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks jamasp-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