Which versions of paws-room-acoustics-simulator are malicious?

The following PyPI versions of paws-room-acoustics-simulator are flagged malicious: 99.6. Treat any of these as compromised.

How do I remediate paws-room-acoustics-simulator if I installed it?

paws-room-acoustics-simulator 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 paws-room-acoustics-simulator — how do I know if it already compromised me?

If paws-room-acoustics-simulator 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 paws-room-acoustics-simulator part of a known attack campaign?

Yes — paws-room-acoustics-simulator is associated with the 2024-11-byted-dast 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 paws-room-acoustics-simulator 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 paws-room-acoustics-simulator (version 99.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paws-room-acoustics-simulator across your stack and pipelines.

Malicious package

paws-room-acoustics-simulatorPyPI

Malicious code in paws-room-acoustics-simulator (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10828

Immediate action

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

pip uninstall paws-room-acoustics-simulator

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'paws-room-acoustics-simulator' @ 99.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.6

Indicators of compromise (SHA-256)

c3f8249684bf7b77429ca0e1f687e151959b9a8f2783b500b6b625163f136d57

32f6a48aa5acf1f6dccdbd938f720b6eaf3d1aea2f7f95db8cea1887aef32e91

445343e49b96223100e6e2d17e72f3cead8dedeeac8f6250e2b3b66b52c694e4

7dcc07cc5ab2e784f062fa36af5a7993385e74781e1439d4aab27895703e62ee

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks paws-room-acoustics-simulator-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