Which versions of rowrapee are malicious?

The following PyPI versions of rowrapee are flagged malicious: 1.21, 1.22. Treat any of these as compromised.

How do I remediate rowrapee if I installed it?

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

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

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

Malicious package

rowrapeePyPI

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

MAL-2026-2122

Immediate action

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

pip uninstall rowrapee

What this malware does

The package hides code to download and start malicious script containing malware, identified as adware. The triggering method seems to be PTH file, although it's not always present

Given the time correlation, it's likely armored continuation of 2026-03-robloxapi-testy

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

Campaign: 2026-03-rowrap

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware

Malicious versions

2 flagged

1.211.22

Indicators of compromise (SHA-256)

398cfbdac2d3602a5c9836408942993c3f2bbcda911184825f01cf9937fb035e

d10d05b75c1cd832c14ae533bd625e9d637916e38bea3bd9a589c70cd377aae1

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

Campaign

2026-03-rowrap

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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