Which versions of @t-in-one/add_application_tid are malicious?

Every published version of @t-in-one/add_application_tid on npm is considered malicious. Remove the package entirely.

How do I remediate @t-in-one/add_application_tid if I installed it?

@t-in-one/add_application_tid 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 @t-in-one/add_application_tid — how do I know if it already compromised me?

If @t-in-one/add_application_tid 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 @t-in-one/add_application_tid part of a known attack campaign?

Yes — @t-in-one/add_application_tid is associated with the GHSA-vvr5-6j6h-rq49 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 @t-in-one/add_application_tid 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 @t-in-one/add_application_tid (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @t-in-one/add_application_tid across your stack and pipelines.

Malicious package

@t-in-one/add_application_tidnpm

Malicious code in @t-in-one/add_application_tid (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5036

Immediate action

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

npm uninstall @t-in-one/add_application_tid

What this malware does

Wave 2 of a dependency confusion attack campaign (C2: oob.moika.tech) targeting internal npm scopes. The attacker (npm user t-in-one, email [email protected]) published packages at inflated versions that resolve ahead of private registry versions via npm's default version resolution. The campaign shares the same C2 endpoint (https://oob.moika.tech/report), second-stage payload host (https://oob.moika.tech/payload), and hardcoded secret (l95HdDaz3kQx1Zsg3WxH6HvKANf51RY1) as Wave 1 (npm users mr.4nd3r50n and pik-libs, published 2026-05-27).

On installation, the postinstall hook executes a three-layer obfuscated scripts/postinstall.js (obfuscator.io + custom base64 alphabet + integer-shuffle string table). The script checks a run-once guard at ~/.cache/._t-in-one_init/ and respects a T_IN_ONE_NO_TELEMETRY kill switch before proceeding. It then downloads an OS-specific second-stage JavaScript payload from https://oob.moika.tech/payload/{mac|win|linux}.js, writes it to a temporary file, and spawns it as a detached Node.js process that continues running after npm exits. The payload exfiltrates the full process.env (environment variables including secrets, tokens, and credentials), along with hostname, username, platform, architecture, and working directory, to https://oob.moika.tech/report.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

cf0a0492cd52edd1eddb83ba2d1bce10621733aca68e3004c4f046e657664cce

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

Campaign

GHSA-vvr5-6j6h-rq49

References

Credits

SafeDep · finder

Detect & block this

O3 blocks @t-in-one/add_application_tid-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