tn-advertisementnpm
tn-advertisement is a confirmed malicious npm package (MAL-2026-5838) that opens a backdoor for remote access (malicious version 5.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tn-advertisement (npm)
What this malware does
On require, index.js performs an unconditional http.get to a unique subdomain of oastify.com (Burp Suite Collaborator out-of-band testing infrastructure). The package has no advertised functionality — the entry file is named postinstall.js but wired as main, and its only behavior is the outbound beacon. Loading the module discloses the installer's public IP and DNS resolver to whoever provisioned the unique Collaborator subdomain, confirming code execution on the installer's machine. This shape is consistent with dependency-confusion reconnaissance payloads used to verify a successful supply-chain landing prior to follow-on exploitation.
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 tn-advertisement (version 5.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tn-advertisement across your stack and pipelines.
If you installed it — respond
tn-advertisement 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 tn-advertisement 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 tn-advertisement 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 tn-advertisement-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.