Which versions of netspear are malicious?

The following PyPI versions of netspear are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate netspear if I installed it?

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

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

Yes — netspear is associated with the RLMA-2025-03018, 2025-05-requestpackat, RLUA-2026-00554 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 netspear 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 netspear (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging netspear across your stack and pipelines.

Malicious package

netspearPyPI

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

MAL-2025-5121

Immediate action

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

pip uninstall netspear

What this malware does

Code download and runs an executable, which is widely recognized as malware. The system is also configured to run it on startup, and the file is saved in paths attempting to look as a system file.

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

Campaign: 2025-05-requestpackat

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
peristence-autorun

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

ea6eda20b9944f3c64f2b1317d7f52b997e99a7292e7e95a5e3718158fd1509b

075f67a838fbfebdad8179a87410b65d43e616d4889db07537d92ed5456975cf

015d4e7a345166ce5767408055a810a394e59a8c40b1a3c459ee006efa647e0a

54764f23fdbdff7f6b6600a5c3f9a07d7dbf57a820f29cc2c290c42a28200b00

130385d02adbd04e3924dc9d995864ab3bfbeea181db0460889ae885218126d5

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

Campaign

RLMA-2025-030182025-05-requestpackatRLUA-2026-00554

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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