Which versions of rowrap are malicious?

The following PyPI versions of rowrap are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.5, 1.1.6, 1.1.8, 1.20, 1.21. Treat any of these as compromised.

How do I remediate rowrap if I installed it?

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

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

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

Malicious package

rowrapPyPI

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

MAL-2026-1544

Immediate action

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

pip uninstall rowrap

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

15 flagged

1.0.01.0.11.0.21.0.41.0.81.0.91.1.01.1.11.1.21.1.31.1.51.1.61.1.81.201.21

Indicators of compromise (SHA-256)

606ce541a3ef4a98e4e1639e96c6431e7ec83be6f987c640a63c03991eae4f6e

aa14a24775db29bdb8ff5f2e696e0499d404549e6e51f7b4b891973def89ce9f

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 rowrap (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rowrap across your stack and pipelines.
If you installed it — respond
rowrap 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 rowrap 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 rowrap 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. rowrap on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.4, 1.0.8, 1.0.9, 1.1.0, 1.1.1, and 7 more 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) · reporter

Detect & block this

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