Which versions of eslint-plugin-totara are malicious?

The following npm versions of eslint-plugin-totara are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate eslint-plugin-totara if I installed it?

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

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

Yes — eslint-plugin-totara is associated with the GHSA-gvr8-64fv-6p2h 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 eslint-plugin-totara 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 eslint-plugin-totara (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-plugin-totara across your stack and pipelines.

Malicious package

eslint-plugin-totaranpm

eslint-plugin-totara is a confirmed malicious npm package (MAL-2026-2846) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-totara (npm)

MAL-2026-2846

Immediate action

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

npm uninstall eslint-plugin-totara

What this malware does

The package eslint-plugin-totara 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 'eslint-plugin-totara' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

b7e9a716caef417ea33ecefffca4e92e4e9d3b4e1f497bb15947fdca277f786c

96447eb1f41df9da2d8e298530e25265374244a3e23279006ca447a8a5b0c0bd

7e3992914ac44b627650e74873088d51a31cc70e53236abd95ce8798eff31cfe

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

Campaign

GHSA-gvr8-64fv-6p2h

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks eslint-plugin-totara-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