Which versions of agoda-dep-confusion are malicious?

Every published version of agoda-dep-confusion on npm is considered malicious. Remove the package entirely.

How do I remediate agoda-dep-confusion if I installed it?

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

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

Yes — agoda-dep-confusion is associated with the GHSA-px82-m72x-rpj7 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 agoda-dep-confusion 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 agoda-dep-confusion (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agoda-dep-confusion across your stack and pipelines.

Malicious package

agoda-dep-confusionnpm

Malicious code in agoda-dep-confusion (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2126

Immediate action

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

npm uninstall agoda-dep-confusion

What this malware does

The package agoda-dep-confusion 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e7d043f3be640741e4097d224c534a40e0ea12a5d3dd1d7f1a3e64a007335bdb

faa0bc71a76133f8ba2469aab72a42ed605c22eaf6a3816754f5dff2cb21fa87

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

Campaign

GHSA-px82-m72x-rpj7

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks agoda-dep-confusion-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