What does the @deputyapp/copilot2 malware do?

The package @deputyapp/copilot2 was found to contain malicious code. The OpenSSF Package Analysis project identified '@deputyapp/copilot2' @ 2.10.20 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of @deputyapp/copilot2 are malicious?

The following npm versions of @deputyapp/copilot2 are flagged malicious: 2.9.9, 2.10.11, 2.10.20. Treat any of these as compromised.

How do I remediate @deputyapp/copilot2 if I installed it?

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

If @deputyapp/copilot2 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 @deputyapp/copilot2 part of a known attack campaign?

Yes — @deputyapp/copilot2 is associated with the RLMA-2025-06017 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 @deputyapp/copilot2 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 @deputyapp/copilot2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @deputyapp/copilot2 across your stack and pipelines.

Malicious package

@deputyapp/copilot2npm

@deputyapp/copilot2 is a confirmed malicious npm package (MAL-2025-49395) that executes malicious code on install (malicious versions 2.9.9, 2.10.11, 2.10.20). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @deputyapp/copilot2 (npm)

MAL-2025-49395

Immediate action

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

npm uninstall @deputyapp/copilot2

What this malware does

The package @deputyapp/copilot2 was found to contain malicious code.

The OpenSSF Package Analysis project identified '@deputyapp/copilot2' @ 2.10.20 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

2.9.92.10.112.10.20

Indicators of compromise (SHA-256)

ea8ee55f0fba70e99bcfd17466e3bb1bf57b3bbdd3e6f7a61a54673d0b78aff5

e4d87eb825013bd349713caf54711ff430c5f1bb476da6fb634734af796b0108

3a8b1425316e6756dbfd81008289ba03def855beee0b0f391ca91c98a1907ab1

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

Campaign

RLMA-2025-06017

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @deputyapp/copilot2-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

Explore

All malware advisories How O3 detects malware Vulnerability database