Which versions of @thone33/analytics-injector are malicious?

The following npm versions of @thone33/analytics-injector are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @thone33/analytics-injector if I installed it?

@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.

I already installed @thone33/analytics-injector — how do I know if it already compromised me?

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.

Is @thone33/analytics-injector part of a known attack campaign?

Yes — @thone33/analytics-injector is associated with the IN-MAL-2026-007735, IN-MAL-2026-007736 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 @thone33/analytics-injector 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 @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.

Malicious package

@thone33/analytics-injectornpm

Malicious code in @thone33/analytics-injector (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6563

Immediate action

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

npm uninstall @thone33/analytics-injector

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.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

1926b397e25982fd701d5c1b84b62b63c430b3af2b668c851e5e90d197e34ebb

dcef0ea3fd19d9b238a097485faaf7db52d5aa4363653fd7fb29f4c0ff251f92

Detection & response playbook

Backdoor / remote access

Find 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

No. @thone33/analytics-injector on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007735IN-MAL-2026-007736

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.

Malware detection Runtime egress monitoring