How do I remediate 1q847 if I installed it?

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

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

Yes — 1q847 is associated with the 2026-01-old-1q847 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 1q847 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 1q847 (24 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 1q847 across your stack and pipelines.

Malicious package

1q847PyPI

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

MAL-2026-443

Immediate action

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

pip uninstall 1q847

What this malware does

Package contains two DLL libraries, one of them packed. Both are widely recognized as malware. The exact behavior is not known

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

Campaign: 2026-01-old-1q847

Reasons (based on the campaign):

malware
obfuscation

Malicious versions

24 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.1.00.1.10.2.00.3.00.4.00.5.00.6.00.7.01.0.01.1.01.1.11.1.31.1.41.1.51.1.61.1.71.1.8

Indicators of compromise (SHA-256)

fe398aee3ca61989d1610e4b2edae183ef70d5fabc08709875ca9ef8725d82c5

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 1q847 (24 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 1q847 across your stack and pipelines.
If you installed it — respond
1q847 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 1q847 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 1q847 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. 1q847 on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.1.0, and 16 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-01-old-1q847

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks 1q847-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