Which versions of unified11 are malicious?

The following npm versions of unified11 are flagged malicious: 10.0.2. Treat any of these as compromised.

How do I remediate unified11 if I installed it?

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

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

Yes — unified11 is associated with the GHSA-cpc6-mh8p-x65h 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 unified11 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 unified11 (version 10.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unified11 across your stack and pipelines.

Malicious package

unified11npm

Malicious code in unified11 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192259

Immediate action

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

npm uninstall unified11

What this malware does

The package unified11 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.

The OpenSSF Package Analysis project identified 'unified11' @ 10.0.2 (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

1 flagged

10.0.2

Indicators of compromise (SHA-256)

eda3f5f03cef0c612b0168424f40b8f3c9c8a79bec6e192bb96e8c51c0d67761

2da60b6c513002dadf0ea32c3293c0c1f0e73d8db20f85baf9b207fff1311569

0234999818b5c6447b46c2551778c8daea15a41767afd1270af691c637d8ea9d

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

Campaign

GHSA-cpc6-mh8p-x65h

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks unified11-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