Which versions of graphemer are malicious?

The following PyPI versions of graphemer are flagged malicious: 3.1.2. Treat any of these as compromised.

How do I remediate graphemer if I installed it?

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

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

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

Malicious package

graphemerPyPI

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

MAL-2025-6516

Immediate action

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

pip uninstall graphemer

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

3.1.2

Indicators of compromise (SHA-256)

92546a058a1936d96baca4937ad8c7ee03e05da18ec7a13157c5d25e48ff6372

383393732030c3a69636193e5bfb774b4450d87a57d28d14e1011fe5cc0360db

2a602bedb500f9fdb4029022aae5636875ba2f45f6ffe2a4d046a7bf1155a50e

5669bbd08960eb401b20c72c0a85bccb0372c85f9418b7cd6fec9e9958c7e429

20aa4d1f79d3ca94b98bf4e0bc0cc01097ee492364e5c93511b7365247c4538d

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

Campaign

RLMA-2025-03607GENERIC-standard-pypi-install-pentestRLUA-2026-00365

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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