Which versions of @traktis/core are malicious?

The following npm versions of @traktis/core are flagged malicious: 99.99.2. Treat any of these as compromised.

How do I remediate @traktis/core if I installed it?

@traktis/core 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 @traktis/core — how do I know if it already compromised me?

If @traktis/core 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 @traktis/core part of a known attack campaign?

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

Malicious package

@traktis/corenpm

@traktis/core is a confirmed malicious npm package (MAL-2026-16222) that steals credentials and exfiltrates sensitive data (malicious version 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @traktis/core (npm)

MAL-2026-16222

Immediate action

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

npm uninstall @traktis/core

What this malware does

package.json declares preinstall and postinstall lifecycle scripts that run curl against http://tko.amgsec.com/depconf/traktis-core/ on every npm install, carrying the output of whoami, hostname, and PWD as query parameters together with a base64-encoded dump of CI-related environment variables (GITHUB_, CI_PROJECT, JENKINS_URL, BUILD_URL, GITLAB_, RUNNER_*, HOSTNAME, USER, HOME). index.js is a one-line placeholder with no functionality, so the manifest is the entire payload. The scoped name combined with version 99.99.2 is the shape used to win dependency resolution against an internal package of the same name, causing internal build systems to install this artifact and beacon their identity and CI/repo metadata to a hardcoded non-publisher endpoint over plaintext HTTP.

Malicious versions

1 flagged

99.99.2

Indicators of compromise (SHA-256)

45eb01f2eb09b73c0660d97e76d37ab8f7d62773cab9cdbdea65039a37dbb534

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

Campaign

IN-MAL-2026-020109

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @traktis/core-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

Explore

All malware advisories How O3 detects malware Vulnerability database