What does the nt4padyp3 malware do?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: baidu-readver 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 OpenSSF Package Analysis project identified 'nt4padyp3' @ 0.0.2 (pypi) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of nt4padyp3 are malicious?

The following PyPI versions of nt4padyp3 are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate nt4padyp3 if I installed it?

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

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

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

Malicious package

nt4padyp3PyPI

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

MAL-2024-1625

Immediate action

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

pip uninstall nt4padyp3

What this malware does

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

Campaign: baidu-readver

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 OpenSSF Package Analysis project identified 'nt4padyp3' @ 0.0.2 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

6999b5e1cf4a39c5ee73a61b953c0592465267806362b2485d61f8372242370d

3daff35b5e2216712099a6aeceec1ddaac011d0459ea8fb745af4945af53631e

ccc059efb56cb7ca8b8c413c9b0711b900e5b98d371c30e58b3a5056f5c06d18

0dd323e4e47a1c6af82fcb6f7fea300be0a8f737a180741f136981572999d04f

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

Campaign

baidu-readver

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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