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

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

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

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

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

Yes — @team-event/models is associated with the GHSA-993g-929w-5v55, RLMA-2025-04901, RLUA-2026-01064 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/models 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/models (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/models across your stack and pipelines.

Malicious package

@team-event/modelsnpm

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

MAL-2025-47048

Immediate action

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

npm uninstall @team-event/models

What this malware does

The package @team-event/models 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)

6769b5703bfb1b74cb1db2c7bf3e87a4abfcc35e4e3fd588c284080cb96583e2

159bbe205006c9c45e0eb1859e0b0b3dc12ae2547c7ca54766b1d83b6d1cf2a2

183b2b3e1dc4058fdc47d90cb65a74a212881256769a5e1769f80500bdadb4e1

c4f1b17f6d7b39cdfe4feeead8f87dbfcc96a781777a5d6d635a8975f0eefc32

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/models (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/models across your stack and pipelines.
If you installed it — respond
Remove @team-event/models 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/models 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/models 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/models 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-993g-929w-5v55RLMA-2025-04901RLUA-2026-01064

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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