How do I remediate notoken887 if I installed it?

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

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

Yes — notoken887 is associated with the RLMA-2024-11104 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 notoken887 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for notoken887 (79 malicious versions).

Malicious package

notoken887PyPI

notoken887 is a confirmed malicious PyPI package (MAL-2024-11648) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 1.1.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in notoken887 (PyPI)

MAL-2024-11648

Immediate action

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

pip uninstall notoken887

Malicious versions

79 flagged

0.1.00.1.11.1.51.1.61.1.81.1.91.21.211.221.22.11.22.31.22.41.22.51.22.61.22.71.22.81.22.91.23.01.23.11.23.31.23.41.23.51.23.61.23.71.23.91.24.21.24.31.24.41.24.51.24.61.24.71.24.81.24.91.25.11.25.21.25.31.25.51.25.61.25.71.25.91.26.11.26.21.26.31.26.41.26.6.2.31.26.6.2.3.11.26.71.26.81.26.91.26.101.26.111.26.121.26.131.26.141.26.151.26.161.26.171.26.181.26.191.26.201.26.211.26.221.26.231.26.241.26.251.26.261.26.271.26.281.26.291.26.301.26.311.26.321.26.331.26.341.26.351.26.361.26.371.26.391.26.40

Indicators of compromise (SHA-256)

3d0cff28964f357890c4bf1bcebe3c331c13b54cf1eae4c054b575401a85a313

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for notoken887 (79 malicious versions).
If you installed it — respond
notoken887 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 notoken887 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. notoken887 on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 1.1.5, 1.1.6, 1.1.8, 1.1.9, 1.2, 1.21, and 71 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11104

Credits

ReversingLabs · finder

Detect & block this

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