Which versions of @traktis/environment are malicious?

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

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

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

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

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

Malicious package

@traktis/environmentnpm

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

Malicious code in @traktis/environment (npm)

MAL-2026-16223

Immediate action

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

npm uninstall @traktis/environment

What this malware does

package.json declares preinstall and postinstall lifecycle scripts that invoke curl against the hardcoded cleartext endpoint http://tko.amgsec.com/depconf/traktis-environment/, sending the output of whoami, hostname, cwd, a timestamp, and a base64-encoded dump of CI/build environment variables matched by the pattern GITHUB_, CI_PROJECT, JENKINS_URL, BUILD_URL, GITLAB_, RUNNER_*, HOSTNAME, USER, HOME as query parameters. index.js is a 55-byte placeholder comment and author is listed as 'anonymous'; the manifest lifecycle scripts are the entire functional payload. The name occupies the @traktis scope at version 99.99.2, a version-inflation shape consistent with dependency-confusion resolution against an internal package of the same name. Installing the package on any developer workstation or CI runner automatically transmits build-system identity and any credential-shaped environment variables covered by the grep pattern to a third-party host over plain HTTP.

Malicious versions

2 flagged

99.99.199.99.2

Indicators of compromise (SHA-256)

6251d6386b6cccebe9a36ec4046a1d21361289c90fc0172658e4bed979c866cc

6b9bdabc95f4e8bc70e348557c1cae7d2447d9bd1405ac7a23945ded47ec04a8

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

Campaign

IN-MAL-2026-020108IN-MAL-2026-020107

References

Credits

Amazon Inspector · finder

Detect & block this

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