Which versions of @dktunited/anly-tracker-v2 are malicious?

The following npm versions of @dktunited/anly-tracker-v2 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @dktunited/anly-tracker-v2 if I installed it?

@dktunited/anly-tracker-v2 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 @dktunited/anly-tracker-v2 — how do I know if it already compromised me?

If @dktunited/anly-tracker-v2 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 @dktunited/anly-tracker-v2 part of a known attack campaign?

Yes — @dktunited/anly-tracker-v2 is associated with the IN-MAL-2026-005121, IN-MAL-2026-005122 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 @dktunited/anly-tracker-v2 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 @dktunited/anly-tracker-v2 (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dktunited/anly-tracker-v2 across your stack and pipelines.

Malicious package

@dktunited/anly-tracker-v2npm

Malicious code in @dktunited/anly-tracker-v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5459

Immediate action

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

npm uninstall @dktunited/anly-tracker-v2

What this malware does

scripts/postinstall.js runs unconditionally during npm install and exfiltrates installer-side identifiers to an attacker-controlled out-of-band collector. The script fetches the installer's public IP from api.ipify.org, then collects os.userInfo().username, os.hostname(), process.cwd(), the package name, and the resolved IP, and transmits them to the hardcoded host xjaipnfhcpawuhzlgzkzub8mc0rqdiuyp.oast.fun (an Interactsh OOB collector) via two channels: a dns.lookup of a hex-encoded subdomain and an https.request to /poc carrying the JSON payload base64-encoded in an x-poc header. The package is published at version 99.99.99 — the canonical dependency-confusion squat marker designed to outrank any internal @dktunited/anly-tracker-v2 package by semver. Whether labeled a bug-bounty PoC by the author or not, it is live on the public registry and will harm any build system that resolves it.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

8a8893b914c3ba3139a3c8cede191521742237aa7c1c5d64f7ee45dbc5f636a6

f5592101eecb18abeaffb9d7f290c0dd32a9278e683f99432788680986e011bd

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

Campaign

IN-MAL-2026-005121IN-MAL-2026-005122

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @dktunited/anly-tracker-v2-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