Which versions of @team-event/v2 are malicious?

The following npm versions of @team-event/v2 are flagged malicious: 1.2.9213. Treat any of these as compromised.

How do I remediate @team-event/v2 if I installed it?

Remove @team-event/v2 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 @team-event/v2 — how do I know if it already compromised me?

If @team-event/v2 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 @team-event/v2 part of a known attack campaign?

Yes — @team-event/v2 is associated with the GHSA-j8cg-574v-gjqc, RLMA-2025-04904, RLUA-2026-01067 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 @team-event/v2 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 @team-event/v2 (version 1.2.9213). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @team-event/v2 across your stack and pipelines.

Malicious package

@team-event/v2npm

Malicious code in @team-event/v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47051

Immediate action

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

npm uninstall @team-event/v2

What this malware does

The package @team-event/v2 was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.2.9213

Indicators of compromise (SHA-256)

cc9d7a4f41e5d6a4af9a15c05d4e0023f5f141a75b5c62d116bb229a1ea7541d

9ced7f49df57d71ee4cb503e65113732a2b67b679e5282f32a5697f772a8ea54

10e3aa86b9b79552d110054ee5a7dbee66156d9abf024d783715f00d15ef64db

6d451da38dd8cf836938dd669e13edea4ad56745bdc3941701fe56849a89c012

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

Campaign

GHSA-j8cg-574v-gjqcRLMA-2025-04904RLUA-2026-01067

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @team-event/v2-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