Which versions of twitter-request-diagnostics are malicious?

The following PyPI versions of twitter-request-diagnostics are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate twitter-request-diagnostics if I installed it?

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

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

Yes — twitter-request-diagnostics is associated with the 2026-10-test-01-rafamarrara-learning-dc 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 twitter-request-diagnostics across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for twitter-request-diagnostics (version 1.0.0).

Malicious package

twitter-request-diagnosticsPyPI

Advisory published Oct 29, 2026Updated Oct 30, 2026

twitter-request-diagnostics is a confirmed malicious PyPI package (MAL-2026-18403) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in twitter-request-diagnostics (PyPI)

MAL-2026-18403

Immediate action

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

pip uninstall twitter-request-diagnostics

What this malware does

Package offers a middleware adding allegedly diagnostic endpoint to a web app. Besides allowing for env variable exfiltration, it also contains a hidden functionality allowing executing sent commands.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-10-test-01-rafamarrara-learning-dc

Reasons (based on the campaign):

backdoor
exfiltration-env-variables

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d437e09d0338d5b7640d3132c723bc4c77d95a052b35f7a32335a1d832c799c1

Detection & response playbook

Credential / info stealer

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

Campaign

2026-10-test-01-rafamarrara-learning-dc

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks twitter-request-diagnostics-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