Which versions of @emilgroup/api-documentation are malicious?

The following npm versions of @emilgroup/api-documentation are flagged malicious: 1.19.1, 1.19.2. Treat any of these as compromised.

How do I remediate @emilgroup/api-documentation if I installed it?

@emilgroup/api-documentation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @emilgroup/api-documentation — how do I know if it already compromised me?

If @emilgroup/api-documentation 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 @emilgroup/api-documentation part of a known attack campaign?

Yes — @emilgroup/api-documentation is associated with the GHSA-wq88-f86r-hgrh 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 @emilgroup/api-documentation 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 @emilgroup/api-documentation (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @emilgroup/api-documentation across your stack and pipelines.

Malicious package

@emilgroup/api-documentationnpm

Malicious code in @emilgroup/api-documentation (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2035

Immediate action

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

npm uninstall @emilgroup/api-documentation

What this malware does

The package @emilgroup/api-documentation 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.

This package was compromised by the CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

2 flagged

1.19.11.19.2

Indicators of compromise (SHA-256)

9576b13d3aaefbc259b6cb9884ca1528d40d49f40b2cc4a91b37e1d33a2143a7

58c245a310d05383d1fdf2e98691e5ea42d0505bdab8e27120537609d6bb4acd

25151e54c9718dfa72de2ed072f606def89e8730a724bd38da926a739ee11a43

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @emilgroup/api-documentation (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @emilgroup/api-documentation across your stack and pipelines.
If you installed it — respond
@emilgroup/api-documentation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @emilgroup/api-documentation 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 @emilgroup/api-documentation 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. @emilgroup/api-documentation on npm has been identified as a malicious package (versions 1.19.1, 1.19.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wq88-f86r-hgrh

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @emilgroup/api-documentation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring