Which versions of marinff-test are malicious?

The following PyPI versions of marinff-test are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8. Treat any of these as compromised.

How do I remediate marinff-test if I installed it?

marinff-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed marinff-test — how do I know if it already compromised me?

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

Yes — marinff-test is associated with the RLMA-2025-01971, RLUA-2025-02513, 2025-03-marinff, RLUA-2026-00496 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 marinff-test 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 marinff-test (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging marinff-test across your stack and pipelines.

Malicious package

marinff-testPyPI

Malicious code in marinff-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2973

Immediate action

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

pip uninstall marinff-test

What this malware does

Installing the package starts a reverse shell. The remote server is, however, set as a local IP, so it's most probably testing

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-03-marinff

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

8 flagged

0.10.20.30.40.50.60.70.8

Indicators of compromise (SHA-256)

1cb3616cbc3da5f19069fca2b3f1ba2cc972b73791fb361b72354c4e9f016286

4af88abe2d21f03ca731b99d10260b01a444c323949c039178c3f3e75c7b47f9

1482d9db58b1d5249855fbeb854c95de3db27f27d2d7caad5ad9f2c96f4d8345

c25b081dd711bcb5076c5fbd0ea034850b8e428fed345d93e60036e0e91c9f66

a4b6e79674f2a4cad89ea6d1e8c985816f1fc3bba0f542de15d3424a4fb530b7

56b48c94c0e264d0c64e2ecb1e8029dd4c283903e99e2bc1b1043dc397f40d83

3cdd7dfc5b8002090b6fa6147c8251554d2de854c66ba9166c91e1e8c0b44d6b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for marinff-test (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging marinff-test across your stack and pipelines.
If you installed it — respond
marinff-test establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If marinff-test 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 marinff-test 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. marinff-test on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01971RLUA-2025-025132025-03-marinffRLUA-2026-00496

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks marinff-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring