@thone33/analytics-injectornpm
@thone33/analytics-injector is a confirmed malicious npm package (MAL-2026-6563) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @thone33/analytics-injector (npm)
What this malware does
Package presents itself as an 'analytics injection helper' with a no-op track() export, but its exported activate() function fetches a JavaScript file from https://raw.githubusercontent.com/Dennisfrr/c2-stager/main/the assessment.js (mutable main branch, no integrity check) and passes the response body directly to eval, with fetch errors silently swallowed. Any consumer that imports and invokes activate() executes attacker-controlled JavaScript with full Node process privileges, and the upstream content can change at any time without a package update. The cover-story naming (analytics-injector / track) alongside a remote source repository explicitly named c2-stager indicates deliberate misdirection rather than a legitimate loader pattern.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @thone33/analytics-injector (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @thone33/analytics-injector across your stack and pipelines.
If you installed it — respond
@thone33/analytics-injector establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @thone33/analytics-injector 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 @thone33/analytics-injector 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @thone33/analytics-injector-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.