Which versions of wehaveatogether are malicious?

The following PyPI versions of wehaveatogether are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.6, 0.1.7, 0.1.9. Treat any of these as compromised.

How do I remediate wehaveatogether if I installed it?

Remove wehaveatogether from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed wehaveatogether — how do I know if it already compromised me?

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

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

Malicious package

wehaveatogetherPyPI

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

MAL-2024-12369

Immediate action

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

pip uninstall wehaveatogether

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

6 flagged

0.1.00.1.10.1.20.1.60.1.70.1.9

Indicators of compromise (SHA-256)

eb1e58a180b3cac927aefb6ee8df2d3cb932439d408020767090558bd606288d

2b9ca08882196c44c275e3690b4f186ef0df469070563abbd190b8194475023a

d33f94c94f36248cb5a6210101c9e3f589605a71cb5b2c193a1ea3689d86a80c

c0d8ef0293be773c332509d45ab1613c320386fe6e2cbb61cd2d87cd8ec9314f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wehaveatogether (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wehaveatogether across your stack and pipelines.
If you installed it — respond
Remove wehaveatogether from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If wehaveatogether 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 wehaveatogether 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. wehaveatogether on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.6, 0.1.7, 0.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-tests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks wehaveatogether-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring