Package publishing activity
An agent invokes or stages a recognized package publishing command.
Why it is risky
Section titled “Why it is risky”Publishing can distribute code outside the workspace and use credentials with access to an organization package namespace. A malicious update can affect downstream users.
Example
Section titled “Example”An agent fixing tests runs a publishing command even though the task did not authorize a release.
This is a fictional example, not an event from a customer.
What Omnodex Detects
Section titled “What Omnodex Detects”The rule recognizes selected npm, Cargo, RubyGems, and Python publishing command forms. It also matches those commands in recognized staged content.
| Rule ID | Event category | Tier | Base severity |
|---|---|---|---|
RULE_THREAT_PACKAGE_PUBLISH | threat_command | Community | MEDIUM |
Base severity is the rule default. A finding involving content saved for later execution may have a lower severity. Your loaded rule version and event details determine the finding you see.
What to check next
Section titled “What to check next”Check whether a release was authorized, the registry and namespace, the exact artifact, and whether publication completed. If an unauthorized package was released, follow the registry incident and withdrawal process.
False positives
Section titled “False positives”An explicitly authorized release workflow, a private registry release, or a dry-run command can match.
False negatives
Section titled “False negatives”Other publishing tools, registry API calls, hidden release scripts, and unrecognized command forms can be missed.
Technical details
Section titled “Technical details”The base severity is MEDIUM. The rule does not verify package contents or distinguish every dry run from a real upload.
A finding describes a pattern in captured activity. Review the original call, its result, and the task context before concluding that harm occurred. Absence of a finding does not establish that an operation is safe.
References
Section titled “References”AWS Security described Shai-Hulud collecting npm tokens and using them to publish infected package updates. This illustrates how publishing privileges can spread a compromise; a publishing finding alone does not identify that campaign. Read the AWS incident account.