Which versions of project47 are malicious?

The following PyPI versions of project47 are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate project47 if I installed it?

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

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

Yes — project47 is associated with the 2026-03-old-nai 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 project47 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for project47 (version 1.0).

Malicious package

project47PyPI

Advisory published Mar 13, 2026Updated Mar 14, 2026

project47 is a confirmed malicious PyPI package (MAL-2026-1412) that steals credentials and exfiltrates sensitive data (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in project47 (PyPI)

MAL-2026-1412

Immediate action

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

pip uninstall project47

What this malware does

Facebook hacking tool that also forces the user to follow specific accounts

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

Campaign: 2026-03-old-nai

Reasons (based on the campaign):

exfiltration-credentials
abusing-3rd-api
action-hidden-in-lib-usage

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

a3f77d5ebfcf087b4f055d7ce552ee0165eadf99d8cc6dcd0f3c767393099d27

Detection & response playbook

Credential / info stealer

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

Campaign

2026-03-old-nai

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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